Peter Neubauer wrote: > One area I am interested in is the possibility to add e.g. automated > clients like the Web CRUD thing for mobile devices, like iPhone, > Android and J2ME. For that, probably the best way to go is a well know > serialization protocol between the server and the client. I guess that > is already in place regarding the Swing integration?
Implicity, yeah. There's an RMI object on the server that is invoked by the client. That interface basically defines the protocol. I plan to replace this with a more generic RemoteInvoker stack though, in order to be able to add more stuff to the call. For example, in SiteVision I could add the set of updated objects as piggyback on a returning call to the applet. The consequence is that if the client calls a Service on the server it will see the results of the server call immediately after the call returns without having to do manual refreshes of the client state. Veeeeeery useful. > Is there any more > work that can be done to e.g. make that changeable, or describe that > network protocol in generic terms so one can build "qi4j cleints" that > can use all the asynchronous server goodies and stil be native to the > client app context (SWT, .NET, J2ME, Android etc)? The "protocol" is going to be RMI-based to start with, i.e. it's not a transport protocol per se, but rather built on top of plain RMI. Which should be fine for at least Android. /Rickard _______________________________________________ qi4j-dev mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/qi4j-dev
