-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric, I think you've found another bug ;) could you open a BZ
entry on this?
- --j.
Eric A. Hall writes:
> Eric A. Hall wrote:
>
> > I'm storing the session variables (such as login status) as part of $self,
> > and storing message variables with
Eric A. Hall wrote:
> 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),
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 thous
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eric A. Hall writes:
> On 3/14/2005 12:32 PM, Daryl C. W. O'Shea wrote:
>
> > There's no need to do your lookups more than once. Save the results the
> > first time you do the lookups/processing.
> >
> > See the SPF.pm plugin for a good example.
>
On 3/14/2005 12:32 PM, Daryl C. W. O'Shea wrote:
> There's no need to do your lookups more than once. Save the results the
> first time you do the lookups/processing.
>
> See the SPF.pm plugin for a good example.
Oh right, it's persistent. Duh.
Thanks
--
Eric A. Hall
Eric A. Hall wrote:
It seems that the plugin architecture only allows a single pass/fail
result, so if you want to have multiple tests with different shades of
results, you have to call the plugin multiple times. Is that right?
Over the weekend I banged together a preliminary ldapBlacklist.pm plugi
It seems that the plugin architecture only allows a single pass/fail
result, so if you want to have multiple tests with different shades of
results, you have to call the plugin multiple times. Is that right?
Over the weekend I banged together a preliminary ldapBlacklist.pm plugin
which lets the m
