[wp-trac] [WordPress Trac] #23099: Add JSON-RPC support using existing XML-RPC methods
WordPress Trac
noreply at wordpress.org
Sun Feb 3 15:59:13 UTC 2013
#23099: Add JSON-RPC support using existing XML-RPC methods
------------------------------------------+------------------
Reporter: maxcutler | Owner:
Type: feature request | Status: new
Priority: normal | Milestone: 3.6
Component: XML-RPC | Version: 3.5
Severity: normal | Resolution:
Keywords: needs-patch needs-unit-tests |
------------------------------------------+------------------
Comment (by redsweater):
maxcutler: as the major proponent of the plan, it seems the onus is more
on you to provide extensive evidence for why such a stop-gap solution
should be implemented, than to put it on markoheijnen and rmccue to
develop an elaborate plan for developing a proper JSON-based API.
Am I right that all the client benefits of the JSON-RPC wrapper you
propose, short of the bandwidth savings, would be achieved by implementing
a similar wrapper on the client side? Maybe that is the right area to
focus on for the short term, to prototype how a JSON-based API should
behave and give you the luxury of dealing in JSON for the majority of your
client code, while exploring the mechanics of how the JSON API should
ideally work.
My general impression of the JSON-RPC wrapper proposal on the server is
that it's an example of "junking up" the code base for a short-term gain.
I think that's the gist of the reaction you are getting from markoheijnen
and rmccue as well. The onus is on proponents to argue that the benefits
of this patch are so great that they override the stop-gap, junking-up
impression it leaves on some of us.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/23099#comment:33>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list