On Wed, 20 Mar 2002, Bill Burke wrote: > > Yes, it is fully portable. I will not use an IOR context, will use the > > IOR object id instead. > > > > So, you can't add abitrary IOR contexts?
The OMG-blessed term is "IOR profile". There is also a thing called "IIOP context", which is a per-message stuff. An IIOP request to some target IOR carries some of the data stuffed into the target IOR (the object key, which includes the object id field), plus zero or more IIOP contexts (data chunks typically used to carry info related with transactions and/or security), plus the actual invocation info (operation and arguments). Any profiles present in the target IOR are _not_ sent along with the request. Hence there is no point in stuffing a container's JMX name within an IOR profile. (I use a profile for codebase info, which is needed at the client side for remote classloading, but is not required to travel within every request.) There is no point in putting the container's JMX name in an IIOP context either, because the context is not a "per IOR" thing. So the JMX name must go within the object id. There is no other place. > Yes :). Wanted to know if ORB's supported "object groups". How will we do > failover if Orbix, TAO, and/or JacORB don't support this feature? I was > hoping that JBoss clustering could support failover for even C++ CORBA > clients. I'll ping my friends at Iona. Anybody know the JacORB or TAO > guys? Iona/Jac/TAO are the main dudes, right? I am in touch with the JacORB folks. Helped them to implement support for RMI valuetypes (a strong requirement for JBoss/IIOP). Will ask about their FT plans. Just checked the TAO site. It supports the FT spec, at least in part. See http://www.cs.wustl.edu/~schmidt/ACE_wrappers/TAO/docs/releasenotes/index.html#fault_tolerance The main free ORBs are JacORB, TAO (C++), MICO (C++) and ORBit (plain C). I think the main commercial dudes are IONA (Orbix) and Borland (Visibroker). > location forward is a good idea. You can use it for load balancing, even without group IORs (which would be needed for high availability). Best, Francisco _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
