The data itself is xmlrpc. Well... the system.multicall (essentially for the reply if i remember correctly my old tests) is perhaps not done in the most used way, but it's not really and clearly documented anywhere, so... and the callbacks are a little specific too, unavoidable.Kw4h wrote:I like the xml-rpc thing in the dedicated server, though there's a big drawback. It's not compatible with Java, and its unfortunately not using the 'standard' xml-rpc.
The transport is not a http-xmlrpc, that's true, and logical, as it is done on a permanent connected socket and not a by request connection, and also the callbacks would not exist with http-xmlrpc.
Onyx is a java program and do tm dedicated xmlrpc for long time. Perhaps Pagaisu and Vegeta would be ok to share the xmlrpc part, you will have to ask them.I tried to get a sample app to connect to the server, and didn't get much further than to the point where you figure out how the protocol really works (raw binary xml over a tcp connection - doesn't really count as xml-rpc but oh well).
Reason why it doesn't work for Java is that there's no support for the 'pack' method, which translates the xml to some binary form.
So I'm wondering: will it ever get full support for xml-rpc?
As slly indicated, Flo made recently some work on java, which at least handle the dialog, coding and xml parsing with the dedicated, and he give the source code, so...