[omniORB] thread creation/deletion interceptors

[Billy Newport]

OmniORB 2.5 lets you add a function which gets called when a thread gets
created. You must then call an OmniORB function to let it continue. When the
thread stops, I think it returns to your function. I use this to add
exception handlers around OmniORB worker threads to let me use ObjectStore
more easily.

omniORB::giopServerThreadWrapper::setGiopServerThreadWrapper(new
ObjectStoreThreadWrapper);


> -----Original Message-----
> From: owner-omniorb-list@orl.co.uk
> [mailto:owner-omniorb-list@orl.co.uk]On Behalf Of Mark Little
> Sent: Wednesday, April 08, 1998 5:15 PM
> To: omniorb-list@orl.co.uk
> Subject: [omniORB] thread creation/deletion interceptors
>
>
> I noticed a while back that someone asked about intercepting thread
> creation and deletion. At the time there was no clean way to do this
> (apart from modifying omniORB2 itself.) Is this going to change? I also
> have a need to know when omniORB2 creates threads on my behalf and when
> they are destroyed.
>
> Mark.
>
> --------------------------------------------------------------------
> SENDER : Dr. Mark Little, Arjuna Project, Distributed Systems Research.
> PHONE  : +44 191 222 8066, FAX : +44 191 222 8232
> POST   : Department of Computing Science, University of Newcastle upon
> 	 Tyne, UK, NE1 7RU
> EMAIL  : M.C.Little@newcastle.ac.uk
>
>