Hi Jorge<div>Thanks for the feedback!!!</div><div>I would really love to see what the mobile team is expecting in XMLRPC improvements.</div><div>I will include these idea in my proposal.</div><div>I posted a draft proposal with the new API in my blog.</div>
<div><meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="http://nprasath.com/wordpress-remote-api/">http://nprasath.com/wordpress-remote-api/</a></div><div><br></div><div>check it there and drop comments.</div>
<div><br></div><div>cheers</div><div><br></div><div><br><br><div class="gmail_quote">On Tue, Mar 22, 2011 at 7:53 PM, Jorge Bernal <span dir="ltr"><<a href="mailto:jorge@automattic.com">jorge@automattic.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Sounds great, XMLRPC could use some love ;)<br>
<br>
I plan to gather some ideas for improvements from the mobile team in<br>
the following weeks.<br>
Besides adding missing features, my main concern right now is trying<br>
to reduce redundant calls and minimize traffic: I'd bet nobody was<br>
thinking of 3G when the api was invented.<br>
<br>
Some ideas for now:<br>
* Add a "since" attribute to methods like wp.getRecentPosts,<br>
wp.getComments, so we can check for new stuff without downloading<br>
everything again. Started at<br>
<a href="http://core.trac.wordpress.org/ticket/16882" target="_blank">http://core.trac.wordpress.org/ticket/16882</a><br>
* wp.getLatestActivity - get posts/comments since a given date. Maybe<br>
even add categories or anything that changed, so syncing would involve<br>
one call only<br>
* wp.quickPost - merge newPost and newMediaObject, so publishing a<br>
picture can be done with just one call. Maybe quickPost is not the<br>
best name for it, but roughly that's the idea<br>
<br>
As for obsolete APIs, many of the wp.* methods use the mw, mt, or<br>
blogger implementations. Nothing should be removed to maintain<br>
compatibility, but the wp.* API should be able to leave those<br>
implementations behind<br>
<br>
On Sat, Mar 19, 2011 at 7:01 PM, prasath nadarajah<br>
<div class="im"><<a href="mailto:n.prasath.002@gmail.com">n.prasath.002@gmail.com</a>> wrote:<br>
</div><div class="im">> Hi hackers,<br>
><br>
> I,m interested in working on extending WordPress xmlrpc capabilities for<br>
> this years GSOC. I came up with some ideas for improving the current API.<br>
> Please let me know what you think of these ideas and possible additions to<br>
> this project. Thank You.<br>
<br>
</div><font color="#888888">--<br>
Jorge Bernal | <a href="mailto:jbernal@gmail.com">jbernal@gmail.com</a> | <a href="mailto:jorge@automattic.com">jorge@automattic.com</a><br>
Mobile Engineer @ Automattic | <a href="http://automattic.com/" target="_blank">http://automattic.com/</a><br>
<br>
<a href="http://jorgebernal.info/" target="_blank">http://jorgebernal.info/</a> | <a href="http://jorgebernal.es/" target="_blank">http://jorgebernal.es/</a> | <a href="http://twitter.com/koke" target="_blank">http://twitter.com/koke</a><br>
</font><div><div></div><div class="h5">_______________________________________________<br>
wp-xmlrpc mailing list<br>
<a href="mailto:wp-xmlrpc@lists.automattic.com">wp-xmlrpc@lists.automattic.com</a><br>
<a href="http://lists.automattic.com/mailman/listinfo/wp-xmlrpc" target="_blank">http://lists.automattic.com/mailman/listinfo/wp-xmlrpc</a><br>
</div></div></blockquote></div><br></div>