Hi Chris,
The Transport uses HTTPChannel which actually does all the communication work of opening, sending/receiving and closing the socket. The Transport layer is supposed to be removed/abstracted from the actual physical acts of opening a socket, etc. and is only responsible for managing these acts. Depending on the action, you will see that the amount of interaction differs. In reality, it is more tightly bound to a http sort of transport, so it should be renamed HTTPTransport, but that's another matter!
Regards,
Fred Preston.
| "Christopher S. Johnson"
<[EMAIL PROTECTED]>
26/10/2005 14:47
|
To: [email protected] cc: Subject: HTTPTransport |
All -
New to axis c but not new to axis, just a quick question so I can better
understand how to build my own transport, I'm sure I'll have more later :)
is the transport module is actually responsible for sending the bytes, in
turn opening the real connection and reading and writing from the socket?
everything is abstracted out so nice it makes it a bit confusing.. how
ironic :)
Thanks
..Chris
