[wp-hackers] XML-based display and spoofing multisite

William Davis will.davis at gmail.com
Sat Jan 15 23:09:41 UTC 2011

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
>> functionality.
> You're going to have a much faster experience using a memory cache  
> ( apc
> and  memcached are the two examples) then a file cache.
> http://www.mysqlperformanceblog.com/2006/08/09/cache-performance-comparison/has
> some comparison data. As with all benchmarks, ymmv.
> http://aaron.jorb.in
> twitter: twitter.com/aaronjorbin
> _______________________________________________
> 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