> I have stuff that might wind up looking like
>
> $rcpt->persistent->{statistics_receivedmsgs_total}++;
>
> $rcpt->persistent->{statistics_receivedstatsbysender}{$NormalizedSenderAddress}++;
Perhaps $rcpt->storage could be provided that could be tied... it just
seems like this is the less conventional accessor in qp-land.
notes('foo') can be accessed with ->{_notes}->{foo}, but this is not the
general convention. When I want to increment a note i just do
$foo->notes( blah => $foo->notes('blah') + 1 ). That said, some of my
colleagues have also complained that notes() even exists as a method and
think it would be fine for it to just be a reserved namespace accessed
directly as a hash key.
> in addition to reading configuration.
Nothing's exactly stopping you from reading configuration directly with a
persistence hook, it just doesn't seem that natural to me, and I think the
needs of a hook_user_config are a subset of the needs of a persistence
hook. I wouldn't really cry if I had to change every $rcpt->config() call
in my codebase to $rcpt->get() or $rcpt->storage() etc, it just seems less
intuitive and less in line with the existing convention of $qp->config()
-Jared
