Hi! > Lack of proper API for required task is our problem. Misuse is not ours. IMHO.
No, it is our problem. We can't just create whatever and throw it over the fence. The properly designed API has to make correct use very easy and incorrect use very hard. That's the point of designing the API, not just giving people means to run random pieces of C code from PHP. With that in mind, the API should be designed so that misuse - especially unintentional misuse - is hard. Not impossible - that we can't do - but hard. It *is* our responsibility. > The best way to perform GC would be cron task. Low traffic sites can > make sure obsolete session is deleted. High traffic site can avoid > occasional slow down by GC. I suppose almost all high traffic sites > uses memcached or like that does not require PHP's session GC at all, > though. Please be aware that the use case you are currently considering - whatever it is, does not matter - is about 0.001% of all use cases, or less. Just because PHP runs on millions of sites with wildly different requirements. So we should support big sites, small sites, slow sites, fast sites, etc. -- Stas Malyshev smalys...@gmail.com -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
