OK then i will start testing next week. I'm working on a social network based on PHP, and really looking forward about implementing Google OpenSocial API.
Keep us notified about your progress :) and "bon courage" as we say :-) Karim 2008/2/21, Chris Chabot <[EMAIL PROTECTED]>: > > Yep that falls under the 'php specific optimizations' part, right now > it re-renders the message bundles, gadget xml's etc ... and there's no > need too really, serialize + store in cache is a wonderful way to > bypass most of the expensive operations. > > Diskcache is oddly fast in a lot of cases (not surprisingly the linux > kernel is incredibly good at keeping file access references and using > memory to cache them based on that) so thats more efficient as a lot > of people would assume, but for multi server deployment that's not a > good option, and shared file systems are horrible with locking and > thus with cache stampeding prevention too. > > Anyhow the short of it is, yes thats high on the list of things to > make (right after proxy/js/rpc servlet porting is done), and i'll > provide a disk and memcached backend's for it right out of the box. > (I'll have to do some swaping with my ZendPlatform bits to include APC > i think, but that should be doable too). > > > -- Chris > > > On Feb 21, 2008, at 8:24 PM, Kevin Brown wrote: > > > You could provide an abstraction here that uses either memcached, > > apc, or > > disk-based caching depending on what's available. APC is pretty much > > guaranteed to be there, and larger orgs would probably want to use > > memcached. > >
