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

prasath nadarajah n.prasath.002 at gmail.com
Wed Mar 23 17:36:21 UTC 2011


That sound great!!!!
Having a flag and retrieving the comment meta values based on that is good.
Mobile clients may chose to omit that to increase response time.

I will modify the proposal accordingly.
Thanks for the suggestion

On Wed, Mar 23, 2011 at 10:57 PM, Eric Mann <eric at eam.me> wrote:

> As you say, the majority of blogs won't use post meta values, so I see this
> need as an edge case.  If a specific plugin is adding comment meta that
> needs to be accessed remotely, that plugin should be handling the extension
> of the API on its own.
>
> But if you were to build this kind of setup, I'd add a flag to the request
> for comments that tells WordPress to return comment meta or not to.  Then
> set that flag to false by default.  Then we have one call that either
> returns meta or not based on your specific needs.
>
> Whether you have two calls on the client end or two queries on the server
> end, you'll always need to do two things ... but make the API as simple as
> possible (one client call) to make it easier to use for a larger number of
> clients.
>
> On Wed, Mar 23, 2011 at 10:21 AM, prasath nadarajah <
> n.prasath.002 at gmail.com> wrote:
>
>> Hi joseph,
>> 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
>>
>>
>> On Wed, Mar 23, 2011 at 9:47 PM, Joseph Scott <joseph at josephscott.org>wrote:
>>
>>> On Sat, Mar 19, 2011 at 12:01 PM, prasath nadarajah
>>> <n.prasath.002 at gmail.com> wrote:
>>> > Adding support to return comment meta values. This has been requested
>>> in
>>> > trac. I think having separate methods for comment meta values is good
>>> rater
>>> > than integrating into comment methods.
>>>
>>>
>>> I don't think we really need separate individual methods for comment
>>> meta data.  For post meta data we expose it via the existing post
>>> management methods.
>>>
>>>
>>> --
>>> Joseph Scott
>>> joseph at josephscott.org
>>> http://josephscott.org/
>>>
>>
>>
>> _______________________________________________
>> wp-xmlrpc mailing list
>> wp-xmlrpc at lists.automattic.com
>> http://lists.automattic.com/mailman/listinfo/wp-xmlrpc
>>
>>
>
> _______________________________________________
> wp-xmlrpc mailing list
> wp-xmlrpc at lists.automattic.com
> http://lists.automattic.com/mailman/listinfo/wp-xmlrpc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.automattic.com/pipermail/wp-xmlrpc/attachments/20110323/8fa06346/attachment.htm>


More information about the wp-xmlrpc mailing list