On 7/29/07, Brian Reichert <[EMAIL PROTECTED]> wrote:
> The symptom I see that after a 'set', subsequent 'gets' show me
> various results; sometimes the data comes back set, sometimes not.
The dbm implementation you're using will not always write everything
to disk until you untie it. To make thi
On Jul 29, 2007, at 12:15 PM, Brian Reichert wrote:
But, that contradicts the behavior I see with my command-line tool
demo:
distinct processes with distinct tied hashes can sucessfully share
data
through the sdbm. :/
any reason why you're using sdbm ? you might be better off with bdb,
On Sun, Jul 29, 2007 at 11:46:20AM -0400, Malcolm J Harwood wrote:
> Your data isn't being shared between the processes, so you're only getting
> the
> data back if your request happens to hit the same apache process.
But, that contradicts the behavior I see with my command-line tool demo:
disti
On Sunday 29 July 2007, Brian Reichert wrote:
> The background: I often use SDBM-tied hashes to share cheap slow
> data across concurrent apps. Not much luck under Mason.
>
> I've cobbled together a Mason handler.pl that maintains such a tied
> hash as a global variable.
>
> I've written a compon
I first posted this on the HTML_Mason mason_users list, as that's
the environment where I first saw this symptom. I though what I
was seeing was an artifact of Mason's caching behavior, but I've
sinec considered it possible that I'm getting bit instead by a core
mod_perl2 behavior under apache 2.0
