Matt Hogstrom wrote:
Not being totally familiar with all the nuances in G WRT to
serialization my comments should be taken with a grain of salt. From my
perspetive there are two major problems with serialized data. One, its
very fragile and two you can't change it if you need to. One could
argue users shouldn't be changing it but in extreme circumstances it is
unavoidable.
I'd vote for the move to XML (ouch, did I say that?)
What protocol should the plugin use to communicate with the server? I
think the only XML based protocol supported by MX4J is SOAP over HTTP.
--
Jeremy
