Bug 392 - remote orb must be consulted for _is_a() on INS objects
Summary: remote orb must be consulted for _is_a() on INS objects
Status: RESOLVED
Alias: None
Product: TAO
Classification: Unclassified
Component: ORB (show other bugs)
Version: 1.0.8
Hardware: All All
: P2 minor
Assignee: DOC Center Support List (internal)
URL:
Depends on:
Blocks:
 
Reported: 1999-12-11 22:26 CST by Chris Hafey
Modified: 2000-09-18 14:47 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 Chris Hafey 1999-12-11 22:26:23 CST 
If you resolve an INS IOR, the repository ID is not set.  This causes the orb
to check with the remote orb *every* time an _is_a() or _narrow() is called on
that object.  If the repository ID is set, this wouldn't be necessary.  I
believe this can be fixed TAO_GIOP_Invocation::location_forward.
Comment 1 Vishal Kachroo 1999-12-12 15:56:59 CST 
I'll take a look at this.
Comment 2 Carlos O'Ryan 2000-09-18 14:47:48 CDT 
Sorry it took me so long to look at this one.  This is not a bug, there is no
way to specify the type_hint for URL-style object references.  So the client ORB
must use _is_a().  This shouldn't be a problem in general because URL-style
object references are intended for bootstrapping a few objects only.
If the application really wants to avoid the _is_a() call then a possible
workaround is to use _unchecked_narrow().