Bug 282 - We need a better interceptor managing mechanism in ORB
Summary: We need a better interceptor managing mechanism in ORB
Status: RESOLVED
Alias: None
Product: TAO
Classification: Unclassified
Component: Portable Interceptors (show other bugs)
Version: 1.0.3
Hardware: All All
: P2 enhancement
Assignee: kirthika
URL:
Depends on:
Blocks:
 
Reported: 1999-08-30 15:28 CDT by Nanbor Wang
Modified: 2001-02-14 02:13 CST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Nanbor Wang 1999-08-30 15:28:54 CDT 
We need a more robust interceptor registerring/unregisterring methods in ORB.

Things need to watch out for are thread-safty, performance and semantics of the
interface.  It's good to provide interface that allows multiple interceptors in
an ORB, however, at this point, it's probably not a good idea to add too much
semantics such as, invocation order/registration order into the interface.
Comment 1 kirthika 1999-08-30 15:43:59 CDT 
Yup, I will take this one.
Comment 2 kirthika 2000-02-26 15:01:59 CST 
This is definitely not going to happen for TAO1.1 !
Hence deferred it for now.