On 6/25/07, Robert Cummings <robert@xxxxxxxxxxxxx> wrote: I presume you mean bytecode caching for #1.
yes
As for application variables... the lack of application level variables is a design choice to make it easier to scale your application horizontally. This is usually referred to as the "shared nothing" approach.
This is interesting; if the lack of application variables is a design decision then why do people look to memcached for performance gains? afaik, the idea is to add support for application variables since php does not provide it inherently. also, other popular (possibly more so in the enterprise [fogive me if you think thats cheesy]) languages namely java and .net have integrated mechanisms to support application variables. this is often sighted as one of the greatest shortcomings of php, in my personal experience. i dont see how lacking support for application variables makes it easier to scale horizontally either. horizontal scaling could be achieved in the same fashion even if the language did offer support for them, by simply choosing not leverage them, if so desired. -nathan On 6/25/07, Robert Cummings <robert@xxxxxxxxxxxxx> wrote:
On Sun, 2007-06-24 at 23:55 -0400, Nathan Nobbe wrote: > Alexander, > > sorry to see nobody has replied to your post, im sure you worked very hard > on the cache system and are eager for feedback.. > > so to me it looks like youve introduced a somewhat new style of caching here > (though im sure there are other such approaches); for instance i know of 2 > main uses for caches at this time [as caching pertains to php]. > > 1. caching php intermediate code > 2. caching application variables > > both of these caching techniques are designed to overcome limitations of the > language as it ships out of the box, more or less; afaik. I presume you mean bytecode caching for #1. As for application variables... the lack of application level variables is a design choice to make it easier to scale your application horizontally. This is usually referred to as the "shared nothing" approach. Cheers, Rob. -- .------------------------------------------------------------. | InterJinn Application Framework - http://www.interjinn.com | :------------------------------------------------------------: | An application and templating framework for PHP. Boasting | | a powerful, scalable system for accessing system services | | such as forms, properties, sessions, and caches. InterJinn | | also provides an extremely flexible architecture for | | creating re-usable components quickly and easily. | `------------------------------------------------------------'
