SPUG: Shared memory system

Peter Darley pdarley at kinesis-cem.com
Thu Dec 6 16:35:17 CST 2001

	IPC::Shareable seems to be closest to doing what I want; is that included
in IPC::Semaphore and it's friends? :)
	I was also considering building a very light shared variables daemon and
module. The daemon would do nothing but deal with setting and retrieving
variables, and the module would handle io and allow tying of variables to
the external variable store.  It seems like this could be very small and
pretty easy to build, but I gotta admit, may have challenges that I don't
foresee and am not equipped to deal with.  Any thought anyone?
Peter Darley

-----Original Message-----
From: Colin Meyer [mailto:cmeyer at helvella.org]
Sent: Thursday, December 06, 2001 2:24 PM
To: Colin Meyer
Cc: Peter Darley; SPUG
Subject: Re: SPUG: Shared memory system

On Thu, Dec 06, 2001 at 02:18:56PM -0800, Colin Meyer wrote:
> The shared memory modules (IPC::*) are difficult to use (don't take well
> to holding Perl data structures), and somewhat buggy (at least on linux,
> under stress testing - I got segfaults) in my experience.

I shouldn't have said IPC::*, I meant IPC::Semaphore and its friends.
There are alot of modules under IPC::* that I haven't played with!


 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
     POST TO: spug-list at pm.org       PROBLEMS: owner-spug-list at pm.org
      Subscriptions; Email to majordomo at pm.org:  ACTION  LIST  EMAIL
  Replace ACTION by subscribe or unsubscribe, EMAIL by your Email-address
 For daily traffic, use spug-list for LIST ;  for weekly, spug-list-digest
     Seattle Perl Users Group (SPUG) Home Page: http://zipcon.net/spug/

More information about the spug-list mailing list