Description:
------------
PHP has built in the ability to persistently keep e.g. database connections. Although it is furthermore possible to cache data and objects e.g. with memcache(d), it is not possible to cache "live" objects which maintain e.g. socket connections, database result sets (i.e. the corresponding resource handles) - as soon as the request process/thread is terminated, all those resources are freed by PHP. 
So my feature request is a function set to
- register an object with PHP as "persistent", with a time-to-live
- "acquire" an object for use in a request (with lock wait timeout)
- "release" an object to give other requests the possibility to use it
- unregister an object (but no immediate destruction, first when it is unset() or the request terminates )

Example: database query which costs a dear cpu-load to execute
E.g. the result set has 200 records which are displayed in pages containing 20 results each, with "next results" and "previous results" links. In a normal PHP application using e.g. a MySQL (or similar) database, the query has to be executed for each click on "next / previous results". 
If the result set was persistent for a reasonably limited time, this unnecessary overhead could be eliminated and thus database server load reduced.
Similar examples could be found for POP3 or IMAP systems, LDAP repositories, large XML files processed piece-by-piece, or objects shared between requests for whatever purpose, and so on.

Or is something like that already existing and I just have not found it?