On Wed, Jul 30, 2008 at 11:42 AM, Ranga Nathan <[EMAIL PROTECTED]> wrote: > Before I go ahead and do something screwy, I thought to ask the public what > they do in this case. I realize that one of the children would get the > message indicating the changes. If it updates the data structure in memory > that would do it only for THAT client, right? In other words, what is the > best way for all the children to share variables?
If you want to guarantee that your application can never scale, then you could use shared memory. If you want your application to be able to run on multiple machines, then I'd suggest that you use memcached. See http://www.danga.com/memcached/, which you can access using the CPAN module Cache::Memcached. Several years ago it had a bug where you couldn't have keys over a certain length. We got around that by just using Digest::MD5 to make short keys to use. I don't know if the limitation is still there or not. Other than that I've never seen a problem with it. But you'll probably want a plain text file to be written out somewhere in the background to preserve data across server restarts. Cheers, Ben _______________________________________________ Boston-pm mailing list [email protected] http://mail.pm.org/mailman/listinfo/boston-pm
