Hello Christian, I guess its a bit early to discuss the reimplementation of the RPC layer because its scheduled for december which is quite a long time. But anyway, I appreciate your thoughts and help because I think I can only profit of your experience in this area. My general idea is to be fully standard compatible so we can use every standard compliant server. I believe that those guys made the spec should have thought about all this issues and had found a good way to get it done. We only have to figure out what they thought. :) Thats my current plan because at the moment I'm not really into that topic of transport layer and RPC and whats additionally needed. Regards, Martin
Am 29.07.2010 um 08:21 schrieb panyasan: > > Since Martin has mentioned that the json-rpc layer will be rewritten to > conform to spec 2.0 and to remove non-standard behavior, I wanted to discuss > the following point ahead of time: > > At least two things are "non-standard" in the current implementation that > Derrell has designed: the JSON date encoding and the "server_data" property > of the jsonrpc request. I don't have strong opinions on the Date issue -- I > know Derrell does ;-) -- but I am relying heavily alot on the server_data > (data sent in addition to the service method request to the server). This > data is used to send session data which is of no interest to the individual > method called, but important for my server to distinguish between > authenticated and non-authenticated requests. > > Since this feature will certainly be removed (not being part of the official > jsonrpc specs), I want to make sure there is a replacement. Since we're > using HTTP, one solution could be to move the server_data into cookies or > HTTP headers which can then be picked up by the server side. > > Any other ideas how json-rpc "meta-data" that might be necessary to keep > state can be implemented compatible with json-rpc? > > Thanks, > > Christian > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/Rewriting-the-JSON-RPC-layer-compatibility-issues-tp5346941p5346941.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > The Palm PDK Hot Apps Program offers developers who use the > Plug-In Development Kit to bring their C/C++ apps to Palm for a share > of $1 Million in cash or HP Products. Visit us here for more details: > http://p.sf.net/sfu/dev2dev-palm > _______________________________________________ > qooxdoo-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel ------------------------------------------------------------------------------ The Palm PDK Hot Apps Program offers developers who use the Plug-In Development Kit to bring their C/C++ apps to Palm for a share of $1 Million in cash or HP Products. Visit us here for more details: http://p.sf.net/sfu/dev2dev-palm _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
