Bug 2063 - Planned changes to direct collocation
Summary: Planned changes to direct collocation
Status: NEW
Alias: None
Product: TAO
Classification: Unclassified
Component: ORB (show other bugs)
Version: 1.4.4
Hardware: All All
: P3 normal
Assignee: DOC Center Support List (internal)
URL:
Depends on:
Blocks: 2454
  Show dependency tree
 
Reported: 2005-03-16 04:00 CST by Nanbor Wang
Modified: 2005-05-31 03:55 CDT (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 2005-03-16 04:00:50 CST 
Changes planned for direct collocation (which was arrived after a discussion
with Ossama, Dr. Schmidt, Johnny and me):

. Direct collocation calls will not be ORB mediate
. Interceptors will not be fired
. Client side interceptors that are getting fired will be turned off

This is to keep direct collocation calls as fast as possible and completely
inconsistent (yes, you read it right -- completely inconsistent) with the spec.
This should appear in the main trunk probably soon.
Comment 1 Ossama Othman 2005-03-16 09:17:36 CST 
To be clear for folks outside of the group, direct collocation is a TAO-specific
feature, and is not defined in the spec.  So we're technically not being
inconsistent with the letter of the spec, but perhaps the spirit of the spec.
Comment 2 Johnny Willemsen 2005-05-31 03:55:08 CDT 
Related to this, the draft 3.1 spec also now has a ProcessingMode Policy with
which can specified whether an requewst interceptor should be called in the
remote, collocated or both paths.