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? Thx +-------------------------------+ +-------------------------------+ | Miro Dietiker | | MD Systems Miro Dietiker | | Dipl. Ing. FH Elektrotechnik | | Alte Zürcherstrasse 10 | | | | 8903 Birmensdorf | | | | | | Mobile: +41 (0)78 707 30 10 | | Geschäft: +41 (0)43 344 03 56 | | | | Fax: +41 (0)43 344 03 57 | | [EMAIL PROTECTED] | | [EMAIL PROTECTED] | | | | www.md-systems.ch | +-------------------------------+ +-------------------------------+ -----Ursprüngliche Nachricht----- Von: Mike Jackson [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 25. November 2005 01:30 An: Miro Dietiker, MD Systems Cc: perl-ldap@perl.org Betreff: Re: Freeing resources? Miro Dietiker, MD Systems wrote: > Hi! > I'm doing series of ldap searches and I'm new on ldap query > implementation. > Compared to database queries (where you get a result which can be freed) > I don't understand the way how to free a message and its associated > resources and can't find any documentation on it. > > Can someone explain me the way to implement searches resource-optimized? > > Is there no internal ldap-protocol-handle of a message which needs to > be freed when no more in usage? You don't allocate and free memory with perl; it's handled automatically. -- mike
