What is the distinction between a transport name and the protocol? By default, it appears that the name is the protocol.
Under what circumstances would the name be changed (Call.TRANSPORT_NAME)? The 'name' doesn't appear to be used for anything (whereas the protocol is used to find the right Transport class. Unless there are objections, I'd like to remove the logic that allows the name to be changed (again, why?), and change/cleanup the logic to refer to protocol instead of name. Comments? ******************************************* Richard A. Sitze [EMAIL PROTECTED] CORBA Interoperability & WebServices IBM WebSphere Development
