Re: Is this a dream?

Richard Lynch wrote: > Okay, a few things to correct in this thread... > > 1. There will be a Zend cache very, very, very soon... I'm not saying an > exact date -- I leave that up to Marketing. But if you see 1/23 on > http://zend.com then that must be right. (If you see it > anywhere else, > ignore it.) > > 2. The cache will make your site *way* faster -- like twice as fast on > machines with fast disk I/O (eg Solaris) and more like 4X on slower disk > OSes (eg Linux). Whether that's worth the price tag to you or not depends > on a lot of factors -- including how much effort/support it is for you to > add another box to your server farm. > > 3. If the source code they use has proprietary Zend source in it, they are > in violation of various copyright laws etc... Doesn't look like any violations. Writing ANY extensions to the PHP stuff now requires at least referencing 'zend' stuff. Nothing I've seen in the code seems to violate any copyrights. I think the statement about 'using zend source code' was a misstatement. > > > 4. The figure was reported in the Jerusalem Post, I think, but I can > neither confirm nor deny its accuracy. Again, that's up to Marketing. > > 5. The Zend Cache will have the Optimizer builtin, I think... At any > rate, the code isn't compiled so much as it's just kept in RAM -- "compile" > tends to mean "create an executable binary file", which this RAM cache > doesn't do. > Apparently the zend cache wouldn't do this either tho - Zend itself already compiles/creates an executable binary 'object'. It's just not written to a file, AFAICT. > > 6. The Zend Cache should not be confused with the Zend Encoder (fka Zend > Compiler) which *will* create a binary file -- but it's not executable, so > we stopped calling it a Compiler. It's a binary-loadable file that protects > intellectual property. It does *not* drastically improve performance, and > should not be purchased as a performance-improvement measure. The Zend > Cache is for performance. The Zend Encoder should be purhcased if you want > to distribute a cool PHP application without releasing source nor becoming > an ISP. > > 7. I'm not sure what they did to mess up include files -- The Zend products > don't have this problem, because the include()s are done on-demand. Include > files are cached independently by the Zend Cache, and maintained as separate > files by the Zend Encoder. > Something that's not been mentioned or discussed at all re: zend cache is memory usage. Does it keep a completely separate shared memory area, or are scripts cached in each Apache child process? 2nd approach might lead to larger memory requirements than would otherwise be necessary. Any info on this? > > Hope that helps some people clarify things in their minds a bit. More > details can be found at http://www.zend.com > -- ========================== Michael Kimsal http://www.tapinternet.com PHP Training courses http://www.tapinternet.com/php