Justin Mason wrote:
> yeah -- as discussed in the Plugin pod docs, the life-cycle of the objects
> you have access to there is:
I'm currently trying to work this so the LDAP session is maintained for
the lifetime of the module. TCP sessions are pretty expensive, and having
hundreds or even thousands of dead sessions lying around in timeout mode
(not uncommon for busy sites) is going to be very undesirable.
I'm storing the session variables (such as login status) as part of $self,
and storing message variables with $permsgstatus. But where do I put the
logout/disconnect code? DESTROY seems to get called after every message
("seems to" but I'm fairly blurry at this point), which causes the session
to get killed after every message. Where am I supposed to put this stuff?
Thanks
--
Eric A. Hall http://www.ehsco.com/
Internet Core Protocols http://www.oreilly.com/catalog/coreprot/
