> Before someone mentions it, yes this is way more of a pain that just > encapsulating the Freenet protocol over SOAP. While I think that SOAP > would be just great as a client protocol, speed is big issue with node > communication, so I am wary.
Damn, you denied me the satisfaction! :-P Since a SOAP implementation would be less of a pain we (meaning I) would be willing to put it together so we can do a bake-off. I'm writing a chapter for Que one web services at the moment so it jives well with my current interests to do it and it might prove useful. SOAP is stateless at present as well (although you can access session information) but that's being worked on as part of the 2.0 spec I believe. > I think you might be able to do this all over a single Keep-alive HTTP > connection, but I'm not quite sure how. HTTP isn't my forte. I'm not too familiar with raw http either so I'd be interested to know if there's a strategy there as well. Are http keep-alives pretty much universally adopted at this point? Will _______________________________________________ Devl mailing list Devl at freenetproject.org http://www.uprizer.com/mailman/listinfo/devl
