I think you can setup HTTPS with minimal problems using java (jdk1.4 has
direct support for https) but I would encourage you to think stateless with
your design...once you open a connection to the server you are taking up a
valuable resource...if you make it persistant then it is no longer a share
ginal Message-
From: Colin Saxton [mailto:[EMAIL PROTECTED]]
Sent: 28 February 2002 09:39
To: '[EMAIL PROTECTED]'
Subject: RE: porting from socket to SOAP
Most implementations of SOAP use HTTP which means the connection is closed
after each client request (or possibly closed). This m
Our system received asynchronous callbacks from B using our own custom
protocol that was similar to HTTP. When we decided to switch to SOAP for
messaging, we also changed the transport to HTTP. HTTP uses a
request-response method of transmission, whereas our systems also
require a solicit-response
lin Saxton
[mailto:[EMAIL PROTECTED]]Sent: 28 February 2002 09:39To:
'[EMAIL PROTECTED]'Subject: RE: porting from socket to
SOAP
Most
implementations of SOAP use HTTP which means the connection is closed after
each client request (or possibly closed). This means that any data sen
Most
implementations of SOAP use HTTP which means the connection is closed after each
client request (or possibly closed). This means that any data sent from the
server must first come from a client request.
It
also depends on the nodes that are communicating. To implement effecient
commu
