[wp-xmlrpc] GSOC Proposal - Extending WordPress Remote API

[prasath nadarajah]

I added some more ideas to the project.

A full proposal can be found here.

http://nprasath.com/wordpress-webservices/

Please give me some feedback on this.

Also suggest ideas that you think useful for external apps

*
*

*Custom Post Types Management*

WordPress 3.0 <http://codex.wordpress.org/Version_3.0> gives you the
capability to add your own custom post
types<http://codex.wordpress.org/Post_Types#Custom_Types> and
to use them in different ways. A generic API for managing posts would be
beneficial include post, pages, nav_menu_items as well as user defined
custom post types.

Custom post type are not stored persistently. So we have do it in each
request. We can save the details as options through xmlrpc and add a
loop increate_initial_taxonomies() method to retrieve custom post
type. See
this paste for reference http://pastebin.com/JhtrjYRA

Same approach can be done for taxonomy management as well.

*Custom Taxonomy Management*

 WordPress 3 gives us fully hierarchical custom taxonomies. Managing custom
taxonomies would using clients be awesome. Same as custom post type a
generic API for managing taxonomies is good as it inclues categories, tags,
post formats, nav_menus as well as user defined taxonomies.

*Support For Mobile Notifications*

 This enables mobile clients to show notifications about the updates in the
blog. A generic method which can accept date-time as an argument and queries
for new posts, comments, user etc and return an array containing the new
changes. This would is possible after improving the search API and also
reduces the bandwidth used by the mobile apps.

 Mobile clients can hold the date-time when they are closed an at opening
they can pass the this argument and retrieve notifications about new
activity thus reducing the usage of bandwidth.

On Fri, Mar 25, 2011 at 1:10 AM, prasath nadarajah
<n.prasath.002 at gmail.com>wrote:

> Did some testing with the above approach and the results are more or less
> the same.
> Comment meta values can be send with wp.getComments method.
>
> patched this ticket
> http://core.trac.wordpress.org/ticket/13835
>
>
> On Thu, Mar 24, 2011 at 1:49 AM, Joseph Scott <joseph at josephscott.org>wrote:
>
>> There is no harm in sending back an empty array for comments that have
>> no meta data.
>>
>> Have you benchmarked these different approaches to determine that it
>> would double the response time?  I don't think it will dramatically
>> increase the over head, but I'd be curious to see test results.  After
>> for sites that cache data I think it the difference will be very, very
>> small.
>>
>> On Wed, Mar 23, 2011 at 11:21 AM, prasath nadarajah
>> <n.prasath.002 at gmail.com> wrote:
>> > what i thought was most of the blog dont use commenta meta value.
>> > post meta values are extensively used, but not comment metas.
>> > If you use the default comment form the comment meta tables will
>> > be empty. my comment meta table is empty i guess this is the case with
>> > most of the blogs including wordpress.com blogs.
>> > Also comments are greater in numbers than posts. typically a famous blog
>> > will have 40-60 comments. so everytime you query for a comment it
>> > will query comments table as well as the comment meta table.
>> > this may possibly double the response time in mobile apps.
>> > seperately querying for meta values when needed is more efficient.
>> > what do you think?
>> > correct me if i,m wrong
>>
>>
>>
>> --
>> Joseph Scott
>> joseph at josephscott.org
>> http://josephscott.org/
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.automattic.com/pipermail/wp-xmlrpc/attachments/20110326/92008eb1/attachment.htm>