Bug 456

Summary:	IMR doesn't support multiple profiles in an IOR
Product:	TAO	Reporter:	Ossama Othman <ossama.othman>
Component:	Implementation Repository	Assignee:	Steve Totten <totten_s>
Status:	NEW ---
Severity:	normal	CC:	mesnierp
Priority:	P4
Version:	1.0.14
Hardware:	All
OS:	All

Description Ossama Othman 2000-02-24 12:14:04 CST

The IMR currently only supports a single IIOP profile in an IOR.  However, once
TAO's support for hosts with multiple network interfaces is committed an
endpoint will be created on each interface for the default case `-ORBEndpoint
iiop://'.  The generated IOR will contain a profile for each endpoint.  The IMR
should be able to handle such an IOR.

Note, that updates to the IORManipulation class may be needed to make this task
easier.

Comment 1 Nanbor Wang 2000-02-28 14:32:59 CST

I don't think this is as high of a priority, as long as the default works.

A lot depends on whether the multiple endpoints can be represented in one
string, since the IMR stores the servers endpoint as one string.  It then takes
the endpoint and attaches the object key to it.  So if we are able to say
something like:

iiop://ringil:5000;ringil:5001/object

then it shouldn't be a problem.

Comment 2 Ossama Othman 2000-02-28 14:42:59 CST

Just a clarification...
The iioploc URL format (not "iiop" :-) supports multiple addrs in the IOR,
e.g.:
	iioploc://1.1@ringil:1234,1.0@ringlebells/objkey

However, since we support protocols other than IIOP in an IOR, creating a signle
URL style IOR that contains mixed protocols is not possible.  Does the
forthcoming "corbaloc" format support this?

Comment 3 Ossama Othman 2003-01-30 12:41:11 CST

Darrell is no longer responsible for the ImR.

Comment 4 Nanbor Wang 2003-02-09 12:07:55 CST

Accepting for tao-support

Comment 5 Ossama Othman 2003-02-18 12:19:33 CST

Accepted.

Comment 6 Johnny Willemsen 2007-02-21 06:53:02 CST

Steve, can OCI check this one?

Comment 7 Chad Elliott 2007-04-04 09:40:14 CDT

As far as I can tell, this is still an issue.

Comment 8 Phil Mesnier 2014-09-02 12:23:59 CDT

I believe this bug relates to the stored partial IOR used by the ImR to synthesize a corbaloc string as the foward-to target. The server composes the partial IOR using the stub's "profile_in_use" value, which limits it to a single profile. That profile may have alternate addresses though.