Ian Bicking wrote:
> Alan Kennedy wrote:
> > Perhaps some pythonista from Web-SIG is most appropriate to advise
> > how JSON-RPC should move forward? After all, we're more accustomed
to
> > server-side stuff than those javascript folks ;-)
>
> Let it die? It is more complicated than necessary, wh
[Alan]
>> [2] Perhaps some pythonista from Web-SIG is most appropriate to advise
>> how JSON-RPC should move forward? After all, we're more accustomed to
>> server-side stuff than those javascript folks ;-)
[Ian]
> Let it die? It is more complicated than necessary, when instead you could
> just
Alan Kennedy wrote:
> [1] But it's a shame they didn't write it on WSGI: then their services
> could have run on the Google compute cloud ;-)
Indeed. After seeing a BaseHTTPServer JSON-RPC server go up on the
Python Cookbook I wrote a WSGI server and made it into a tutorial:
http://pythonpaste.
[Ronny]
>> since json-rpc and xml-rpc basically do the same
>> and the only difference is the content-type (json is more concise),
>> i propose to create a single xml/json-rpc module.
[Graham]
> The problem with the JSON-RPC 1.0 specification was that it wasn't
> always as clear as could have
You probably read that google has released appengine:
http://www.youtube.com/watch?v=bfgO-LXGpTM
but they have disabled video responses. So here is mine anyway.
http://www.vimeo.com/875433
Massimo
___
Web-SIG mailing list
Web-SIG@python.org
