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...
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.