Opened 10 years ago

Closed 10 years ago

Last modified 8 years ago

#12838 closed (wontfix)

Feature Request: Usable JSON-RPC API

Reported by: Oroku Saki Owned by: nobody
Component: Core (Other) Version: master
Severity: Keywords: json-rpc
Cc: Triage Stage: Design decision needed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no


The existing JSON-RPC Django implementations out there are limited and hackish. I've experienced:

this one: (which is simple but not very Django-ish as it uses )

and this one: (which starts out with the right idea of using views, but doesn't seem to Djang-ish upon further investigation:

from jsonrpc import jsonrpc_site
import myproj.myapp.views # you must import the views that need connected into and what is jsonrpc_site?
urls += patterns('', (r'^json/', jsonrpc_site.dispatch))

I think that JSON-RPC is important enough for an official well architected / well documented implementation that works well within the normal functionality of Django but I'm not experienced enough to offer a solution. That said, I am willing to spend a couple weeks working on it, with direction from more experienced programmers on here. (Maybe the existing frameworks are great and I'm too much of an amateur to understand their architecture. If that is the case, let me know and I'll close this and shut up.

My only initial thoughts are:
1) Perhaps the API should allow for an API class of API methods and when you register the class the methods become available.
2) Maybe the focus should be less on JSON-2 or 1.1 specs (since there appears to be some ambiguity in that group anyways) and more on usability and flexibility.

Change History (5)

comment:1 Changed 10 years ago by Oroku Saki

I'm serious about contributing a lot of time to this with the advice of some pros so if this is the wrong place for this request, please help me before deleting it, as I would love to contribute.

comment:2 Changed 10 years ago by Alex Gaynor

Triage Stage: UnreviewedDesign decision needed

I'm of the opinion that this shouldn't be something in Django itself, marking as DDN.

comment:3 Changed 10 years ago by Oroku Saki

If somebody with experience in this area can help me spec this out, I will build it. I can code and have quite a bit of OOP experience (ie, I write good code), but I have little JSON-RPC experience. Seeing how popular all API related technologies are becoming, it would be nice to have a well implemented well interfaced version.

The middleware version I mentioned doesn't allow for access to request so you get no easy session access, no URL based queries (like Needless to say, this is not ideal.

comment:4 Changed 10 years ago by Oroku Saki

Resolution: wontfix
Status: newclosed

After much searching, I've come across the holy grail: Closing this ticket.

comment:5 Changed 8 years ago by Jacob

milestone: 1.3

Milestone 1.3 deleted

Note: See TracTickets for help on using tickets.
Back to Top