Am 03.08.2011 09:35, schrieb Lester Caine:
I think this is were I am sitting at the moment ... If a script needs to tidy up memory because something has gone wrong, then in my book the script is faulty? The example of why it is needed does not make sense to me, probably because I don't understand it, firing an action on the database end and trying to then simply tidy up the the php end cache without a clean reload just seems wrong? How do you know what the stored procedure/trigger/business logic has done to the underlying data? But I've never used MySQL :)
I think you might have misunderstood the use case Hannes mentioned. It is a valid problem and weak references are a neat and indeed the only clean solution (so far) to it. I ran into similar Problems and it costs a lot of code and bugfixing to work around the problem, both with the observer-pattern and object-mapper-cache. Do not ridicule his strategy just because you've never run into the problem.
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
