<html><body style="font-family: Helvetica,Arial,sans-serif; font-size: 12px;"><br><div>Oh,</div><div><br></div><div>We seem posted at the same time!</div><div><br></div><div>Thanks for this. I'll give process_info(self()) a try.</div><div><br></div><div>Good work with the library. Regards.</div><div><br></div><div>- Edmond -<br></div><div><br></div><blockquote class="atmailquote"><br>----- Original Message -----<br><div id="origionalMessageFromField" style="width:100%;display:inline;background:rgb(228,228,228);"><div style="display:inline;font-weight:bold;">From:</div> "Fred Hebert" <mononcqc@ferd.ca></div><br><div id="origionalMessageToField" style="display:inline;font-weight:bold;">To:</div>"Edmond Begumisa" <ebegumisa@hysteria-tech.com><br><div id="origionalMessageSentField" style="display:inline;font-weight:bold;">Cc:</div><erlang-questions@erlang.org><br><div style="display:inline;font-weight:bold;">Sent:</div>Wed, 18 Jul 2018 19:17:13 -0400<br><div id="origionalMessageSubjectField" style="display:inline;font-weight:bold;">Subject:</div>Re: [erlang-questions] Dispcount resource identification during init<br><br><br>
On 07/19, Edmond Begumisa wrote:<br>
>Hello all,<br>
><br>
>Any dispcount[1] users out there? Your assistance on two questions <br>
>would be appreciated..<br>
><br>
>a) During init function of the callback module implementing the <br>
>dispcount behaviour, I would like to know resource number assigned to <br>
>that process. Is this possible?<br>
><br><br>
Each process registers itself, so you should be able to find that <br>
information from process_info(self()). Otherwise, nothing is passed <br>
explicitly to the callback.<br><br>
I'm figuring this might be enough to get going.<br><br>
>b) Is this library still active? One feature mentioned on the todo list <br>
>would be nice to have for our purposes (dynamically growing/shrinking <br>
>the number of resources).<br>
><br><br>
It is, for all intents and purposes, a complete library. There has not <br>
been bug reports nor feature requests, so it is stable.<br><br>
If someone were to report bugs, I would probably try and fix them, but <br>
it's been pretty calm and stable for the last 4 years. I haven't used or <br>
tried to use it (my work has moved to systems with different <br>
requirements) recently, but I'm still fine maintaining it.<br><br>
If someone has a plan to improve the libs, I'd be fine handing control <br>
over, though.<br><br></blockquote></body></html>