
Hi all,
Is the format of the echo3 XML transferred between client / server documented anywhere?
I understand it has been cleaned up a lot from echo2 and now is a more like a pure state transfer via XML with no embedded HTML etc etc.
I'm having a bit of an initial look to see if it is feasible to hook another front end onto the echo3 back end ....
Many thanks.
There are no docs I'm aware
There are no docs I'm aware of. You have to work it out from:
It's actually pretty easy to work it all out from these two steps.
Regarding hooking another front end onto the echo3 back end, do you mean like a swing client or something? If so, keep posting your progress, because this is something I also will be doing. I have got as far as a client which successfully transfers the initial client message, but doesn't do anything with it yet :)
Documentation for XML client/server sync format Fri, 07/11/2008
Cool. Thanks. I didn't know about the -Decho.syncdump option. Where does it put the XML and what does it call it?
Re another front end, Yes, something = Flash (Flex). I have previously created an XML driven front end for Flex using a delta model like echo does. It was an internal project so no web sites to look at I'm afraid. I am new to echo and have been delving into the echo2 branch by the guys at http://www.karora.org (the OSGI and eclipse plugin model is what is interesting there).
It is *very* early days and I am really just putting a toe in to see how the echo3 component model, the XML delta protocol, and flex line up.
The first immediate glaring difference is the styling and the way it is handled. I think. :-) I'll try not to offer too much until I get my head into it further lest I get it all wrong!
Btw, thanks for the response. Appreciated.
Output is dumped to the
Output is dumped to the error stream. Please make sure that you do not leave this option enabled for production environments. Every client/server interaction will be logged.
Cheers. Appreciated.
Cheers. Appreciated.