I think it would be nice to be able to publish using either SOAP or RMI,
and provide that option to the user in the server configuration panel in
the tools. I think RMI has better performance once we remote deployment
is supported, but SOAP is more reliable through firewalls, so thats why
it would be good to have it to fall back on.
Jeremy Boynes wrote:
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
