Go for it. I thought about combining these once, but after 5 minutes of
poking about I realized it was more than a 5 minute job, so I decided not
to tackle it just then (ie., I gave up).
org.apache.axis.client.AdminClient makes use of Call.TRANSPORT_NAME, so
SOMEONE is hoping the name is meaningful. What is AdminClient hoping to
accomplish here?
Russell Butek
[EMAIL PROTECTED]
Richard Sitze/Charlotte/IBM@IBMUS on 05/28/2002 06:54:30 PM
Please respond to [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc:
Subject: Re: [axis] Transport Name
Let me add more context: org.apache.axis.client.Transport
*******************************************
Richard A. Sitze [EMAIL PROTECTED]
CORBA Interoperability & WebServices
IBM WebSphere Development
Richard
Sitze/Charlotte/ To:
[EMAIL PROTECTED]
IBM@IBMUS cc:
Subject: [axis] Transport
Name
05/28/2002 05:01
PM
Please respond
to axis-dev
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
