[prev in list] [next in list] [prev in thread] [next in thread] 

List:       jacorb-bugs
Subject:    [jacorb-bugs] [Bug 527] Thread creation during deactivate_object
From:       bugzilla-daemon () inf ! fu-berlin ! de
Date:       2006-09-07 18:49:34
Message-ID: E1GLOwQ-0000Sv-00 () berners ! inf ! fu-berlin ! de
[Download RAW message or body]

http://www.jacorb.org/cgi-bin/bugzilla/show_bug.cgi?id=527





------- Additional Comments From Kevin.Conner@arjuna.com  2006-09-07 20:49 -------
It has been a while since I looked at this code but, IIRC, the whole point of
the thread/thread pool was to allow the deactivate call to return immediately. 
It allowed certain processing to be deferred until there were no references.

I did implement the notification mechanism and this was much cleaner.  The code
has probably moved on since that was done but I could try and dig it out and
update it.



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.


[prev in list] [next in list] [prev in thread] [next in thread]