We are not using it? Why interruption is made by the event fetcher process? Guille
In any case, I'd understand why, but we still have that semaphore installed in the special objects array, and code in the VM for handling it... On Fri, Jun 7, 2013 at 4:31 PM, Guillermo Polito <guillermopolito@gmail.com>wrote:
We are not using it?
Why interruption is made by the event fetcher process?
Guille
On 7 June 2013 16:33, Guillermo Polito <guillermopolito@gmail.com> wrote:
In any case, I'd understand why, but we still have that semaphore installed in the special objects array, and code in the VM for handling it...
There is a single word, explaining everything: legacy. :)
On Fri, Jun 7, 2013 at 4:31 PM, Guillermo Polito <guillermopolito@gmail.com> wrote:
We are not using it?
Why interruption is made by the event fetcher process?
Guille
-- Best regards, Igor Stasenko.
participants (2)
-
Guillermo Polito -
Igor Stasenko