[wp-hackers] XML-based display and spoofing multisite
hempsworth at gmail.com
Sat Jan 15 23:20:26 UTC 2011
What about XML-RPC? Or is that too limited to offer a full API?
Sent from my iPhone
On 15 Jan 2011, at 23:09, William Davis <will.davis at gmail.com> wrote:
> Aaron and Andrew,
> Thanks for your responses. What I'm interested in is how to provide an easily accessible API for everyone, not just internally, especially since we're working hard to field a lot of data for each article. An internal example would be if we want to develop an iPad app, feeding xml files would make more sense than making a direct database call. I've thought about using xmlrpc for this, but that seems ... I dunno. Is there a preferred way of doing something like that?
> In terms of memory cache, it's worth noting that NPR's schematic goes something like database -> memcached -> xml -> memcached
> Also, Andrew, would it be a bad idea to spoof a site like that?
> On Jan 15, 2011, at 5:48 PM, Aaron Jorbin wrote:
>> On Sat, Jan 15, 2011 at 4:36 PM, William Davis <will.davis at gmail.com> wrote:
>>> ..pretty much generating an xml file of everything in order to reduce
>>> strain on the database. It would be great for organizations that want to
>>> offer a robust API to others and/or have lots of delivery systems, such as
>>> different versions of the site, mobile, tablet apps, etc. What are
>>> everyone's thoughts on this sort of delivery system? I'm not advocating
>>> WordPress should adopt it, but I'm sure a plugin could be built to offer the
>> You're going to have a much faster experience using a memory cache ( apc
>> and memcached are the two examples) then a file cache.
>> some comparison data. As with all benchmarks, ymmv.
>> twitter: twitter.com/aaronjorbin
>> wp-hackers mailing list
>> wp-hackers at lists.automattic.com
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers