On Wed, 15 Mar 2006 12:23:38 -0500
Geoffrey Young <[EMAIL PROTECTED]> wrote:
> I actually thing that would be somewhat common. and as I understand
> things, the fix would require the middle step to be
>
> -- next handler
> my $o = $r->pnotes('foo');
> $o->set(bar => 1); # sets $o->{_bar} = 1
> $r->pnotes(foo => $o);
>
> in order for $o to maintain it's internal state. is that right? if
> so, I don't like that very much. in fact, I'll bet that doug
> originally coded pnotes to behave the way it currently does on
> purpose, since the original force behind pnotes was to be able to
> pass objects around.
>
> so, I think I'm leaning more towards "the current behavior is not
> only not broken, it's intentional" camp.
Yes, but I've always seen pnotes as more of a caching/passing
mechanism. Much like Cache::FastMmap or Memcached. Personally,
I would want to middle step to ensure that I really do want that
value to be seen by other handlers.
But maybe I'm the weirdo here and others use pnotes more like
you describe.
---------------------------------
Frank Wiles <[EMAIL PROTECTED]>
http://www.wiles.org
---------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
