HTTPCall,HTTPMessage -> ClientCall,ClientMessage

[Rob Jellinghaus <ro...@unrealities.com>]

I am generifying the HTTPCall and HTTPMessage classes, so as to get rid of
the HTTPCall/TCPCall duplication.

My plan is to make ClientCall be more like a bag of properties which can be
set as appropriate for whatever transport is being used.  HTTPCall's fields
at the moment are URL, user, password, action, and encodingStyle.  Only
encodingStyle is always relevant for all transports.  The TCP (raw socket)
transport currently does not use URL, user, password, *or* action.  In
general there may be lots of transports which don't use those four properties.

So I will create a transportProperties field which will hold all those
optional properties and which will be used as appropriate by downstream
handlers.

I am naming these ClientCall and ClientMessage rather than just Call and
Message in order to avoid confusion between org.apache.axis.client.Message
and org.apache.axis.Message.

This is underway now.  I am in DALNet #ApacheSOAP if anyone wants to chat
about this, or email me.

Cheers,
Rob