Bug 2172 - tao_ft_interception_point has to be removed
Summary: tao_ft_interception_point has to be removed
Status: RESOLVED INVALID
Alias: None
Product: TAO
Classification: Unclassified
Component: Portable Interceptors (show other bugs)
Version: 1.4.6
Hardware: All All
: P3 normal
Assignee: DOC Center Support List (internal)
URL:
Depends on: 1369
Blocks: 2181
  Show dependency tree
 
Reported: 2005-06-27 07:43 CDT by Johnny Willemsen
Modified: 2008-08-20 02:23 CDT (History)
1 user (show)

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 Johnny Willemsen 2005-06-27 07:43:27 CDT 
In TAO I found tao_ft_interception_point which is a method of the server request
interceptors which is TAO specific. A comment said that this needs to be removed
when bug 1369 is fixed. This bug is fixed, so someone has to look when we can
zap this TAO specific method.
Comment 1 Johnny Willemsen 2007-09-25 05:20:33 CDT 
added depends
Comment 2 Simon McQueen 2007-10-15 07:03:58 CDT 
I don't know why the work on bug 1369 was considered to render this interception point unnecessary (perhaps you should svn ann the comment and go and ask the comitter ?).

I do know that this interception point is currently required for successful server side FT operation. We have customers actively using it and so it should not be zapped unless someone can explain to me how else we can return cached results from repeated invocations.
Comment 3 Johnny Willemsen 2007-10-16 00:40:59 CDT 
Simon, if we require this and there is no other way, shouldn't we then raise an OMG issue to this interception point added to spec?
Comment 4 Simon McQueen 2008-08-19 16:05:25 CDT 
Hi Johnny - sorry I missed your comment ages back. 

If you build this extension in I think you trample all over the interceptor flow rules so the PI chapter (and hence all compliant implementations) would need a rewrite. I can't see anyone having the will to do that in all honesty. 

It's an important feature if (and only if) you are trying to put together a 'plugged in' (by means of PI as opposed as hardwired into the ORB) server side FT implementation. TAOs own original FT prototype from a bit back is like this and we have one customer with a similar bit of kit - it's still a bit of a niche market though. For this reason I'd oppose removal without a more compelling motivation than source tidying but think that it staying an optional proprietary extension is fine for us and them right now.

I'd vote resolve invalid to get it off the list. Maybe remove the comment if it's still there.
Comment 5 Johnny Willemsen 2008-08-20 02:23:26 CDT 
closing as invalid, seems to be good reason to keep this