At the risk of me seeming simple and pointless, can I ask why you want
manually code sending serialized objects over HTTP?
What you're doing is reinventing SOAP and XML-RPC. These technologies are
not that hard to use - especially XML-RPC. There are Java libraries
available that handle all the communications for you and just hand your
code XML docs.
Not to mention debugging the application is much easier if you are using
XML because at least it's readable english -
You may also run the risk that you'll code a whole bunch of stuff this way
and then later you'll be asked to refactor them as web services. 'Which is
probably what you should've done to begin with', is what they'll say.
Of course, I could be way off base. From my viewpoint I don't know what
your requirements are -
Kevin
---------------------------------------------------------------------------
This e-mail message (including attachments, if any) is intended for the use
of the individual or entity to which it is addressed and may contain
information that is privileged, proprietary , confidential and exempt from
disclosure. If you are not the intended recipient, you are notified that
any dissemination, distribution or copying of this communication is
strictly prohibited. If you have received this communication in error,
please notify the sender and erase this e-mail message immediately.
---------------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:struts-user-unsubscribe@;jakarta.apache.org>
For additional commands, e-mail: <mailto:struts-user-help@;jakarta.apache.org>
