Hello all, I am happy to announce that Atif Aziz has volunteered to work on the next specs of JSON-RPC. He is currently working on JSON-RPC 1.1 and will be...
The JSON-RPC specification describes a simple yet effective protocol for remote procedure calls based on JSON data. Its lightness is what makes it very...
Thanks for stepping forward Atif. Why not place the draft on the wiki? Then send around announcements and request for comments to groups that might be...
... IMHO the specs should also take into consideration that there is more then simple Functions but OOP in this world. So it would be very nice to have a means...
... The test-form was added as an after-tought, and as such still has many rough edges. But there are some problems I have with asking directly the users...
... more then simple Functions but OOP in this world. ... and/or class a function is in, avoiding the need to write either crappy wrappers or introduce...
... I don't think that the specs should define how method names are to be mapped to the objects handling them. << I agree with Jan here. URI/URLs already...
... My point was rather to have a standard way of handling this so to gain interoperability. It is kind of pointless - imho - to use different mappings for...
... Maybe it might be a good idea to modularize the spec. a. have a lowlevel JSON-RPC communication part b. bindings for existing transport layers(HTTP,...
Hi Matt, I wanted to get the spec to a reasonable first-draft level before publishing. I wanted to use this group to collect the initial feedback on the items...
... namespace/hierarchy That is HTTP transport specific, though. Sooner or later we will have sockets available for web apps. http://www.w3.org/2006/webapi/ ...
I think I will be hanging around on irc://irc.freenode.net/json-rpc and irc://irc.freenode.net/jsolait not sure if one needs to register a channel somewhere if...
Hey, we haven't had so many people in the house in a while. ;) I sense the cogwheels turning and that's great. If I may seem to go silent at times, it's...
... I do dislike HTTP (e.g. 403-Header) based logins since there is no way to do a clean logout. Most if not all bigger websites do use a session based login...
As a long-time xmlrpc user (and json-rpc noob), I think that the overwhelming success that the protocol has seen in real-world usage is in large part to be...
As we provide food for thought, comments and suggestions to be considered for JSON-RPC 1.1, I would urge everyone to use an appropriate subject line so...
... the protocol can be a bit too narrow-minded. Well put. Thinking of a wire protocol as a wire protocol, for use in an RPC and/or Messaging model, is key. ...
... It seems sensible to modularize for the long-run so that various parts can evolve separately, but we want to avoid WS-* for JSON-RPC here, right? If we...
Yes. There is always time later to make it more complex in an effort to make it more simple ;). On a related note, thank you Atif for volunteering and taking...
MPCM
WickedLogic@...
Apr 28, 2006 3:15 pm
215
... You're assuming the protocol is synchronous with no 'window' of outstanding requests, i.e. order of responses matches order of requests. If the message...
... type, making it hard on interoperability (in particular: ok for strings and floats, but what about apps and toolkits that do not support array and object...
... As long as that statement is true (and that's what I'd strongly recommend in any case), it should be fine as any valid JSON type. Then it's up to users to...
... You're that Master Contortionist at the circus, aren't you? :-) WSDL? For XMLRPC? That's like slathering gravel encrusted week old peanut butter on your...
As long as the server app needs to know when the id received is zero to distinguish between notifications and calls, it is hard for the toolkit not to pass the...
Gaetano, ... No. A good example for it are the test forms, for example: http://xins.sf.net/demo/specdocs/myproject/MyFunction-testform.html Thing is, we kept...
... Id must be null for notification(or optionally not present in 1.1), Zero(0) is a perfectly valid id for a request. Matching null against not null should...
Been thinking a bit about the spec over the weekend. Point 1: support for notifications: the current spec is extremely vague on the topic, and there are some...