On 25/11/05 7:57, Miro Dietiker, MD Systems <[EMAIL PROTECTED]> wrote:
> Sure, perl-data-memory ... but (to compare) if you implement filesystem > operations, freeing filehandles after usage is the only right style.. > Same for Handles of Database sockets, since if you have a query handle, > this is not only local memory, but also database server memory which > should be freed wherever possible on a production server. > > Are messages only on client stored memory, not associated with any query > handle of the protocol and ldap-server provided caching? > Especially when I look at async mode, there seems to be some server > resources where we may should be able to free them explicitly? > Or do you simply call unset for messages? Yes, either explicitly unset the Message object, or let it fall out of scope. If you have major issues with memory usage, consider using a callback in the operation (especially the search operation) and handle the results as they arrive one by one. Cheers, Chris
