kimanaw has asked for the wisdom of the Perl Monks concerning the following question:

While scouring CPAN for a means to share objects between threads, I discovered the Pots::* set of modules. However, they're only a first release and about 18 months old wo/ an update. I *think* they'll do what I need (basically, lightweight client/server container classes to permit threaded objects to be passed around), but the docs are a bit lightweight as well.

Context:
I'm looking for a way to encapsulate complex, dynamically created resource objects, esp. DBI objects, in a way that permits them to be passed around to worker threads. I had attempted to implement a Thread::ResourcePool module to accomplish this, but complex objects have (not surprisingly) complex issues wrt shared vs. unshared members. While I'm not a fan of the Storable method Pots::* and its kin rely on to pass data around, the client/server approach certainly simplifies things so I can focus on the core app logic, rather than all the challenges of multithreading/multiprocessing in Perl.

Have any monks used Pots::* ? Any anecdotal experience (either good or bad) much appreciated...

Replies are listed 'Best First'.
Re: Experience w/ Pots::* modules ?
by greenFox (Vicar) on Jul 01, 2005 at 05:22 UTC