[wp-hackers] GSoC Proposal: JSON REST API

Aniket Pant me at aniketpant.com
Fri Apr 12 16:20:04 UTC 2013

I have been looking at this interaction since it started. Actually, I
am also interested in applying for the very same project and I
couldn't help but joining in the discussion.

I love the fact that WordPress put this project on the idea list
because as Ryan said before, "The idea of the GSoC project is to go
from what we have now (i.e. nothing) to something usable." This has
been the motive of most of the GSoC project undertaken by many
students till date and is definitely a good starting point. If
WordPress were to wait for deciding the perfect architecture for
making this API, then it will definitely take a long time. And if
Ryan, or I, or any student for that matter is able to work on API that
pretty much does what the current XML implementation does, then it is
definitely a huge success as we will have a basic foundation ready for
tackling more issues in the future.

And the way Ryan, has defined the basic version of the proposed JSON
API, it works in pretty much the same fashion other APIs do. I doubt
the fact that after a version change, the API will break. The basic
foundation can never change this much to break older applications.


On Fri, Apr 12, 2013 at 5:54 PM, Ryan McCue <lists at rotorised.com> wrote:
> Mike Schinkel wrote:
>> Seeing this I have another concern and that is of implementing the getPost() method as static instead of as the instance method given the difficulty of correctly unit testing static methods[1].
> Sure, but the testing in this case it's probably more likely that we'll
> test over HTTP anyway.
>> I'm not very concerned about pragmatic choices being taken with full understanding of the issues but instead for abritrary choices made because they "seemed like the right way to do it at the time."
> There's certainly no chance of that happening.
>> Can you give an example (where a browser would support "application/json" and thus using "application/vnd.wordpress+json" would be a problem?)  I can't think of a specific one at the moment.
> From memory, older versions of jQuery would need
>> Based on these discussions, and while it pains me I must reverse my earlier endorsement. I think it would be a mistake for WordPress and it's community if this were project were accepted for GSOC.  There are too many decisions that should be considered by more than a small number of eyes to allow a 2 month window to "bake in" it's architecture.
> The idea of the GSoC project is to go from what we have now (i.e.
> nothing) to something usable. Core integration will have further
> considerations for sure; see Bryan's reply for further on this.
>> P.S. Ryan: Please do not feel that I am attacking you in any way.
> This isn't my first rodeo. :)
> --
> Ryan McCue
> <http://ryanmccue.info/>
> _______________________________________________
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-hackers

More information about the wp-hackers mailing list