My conclusions are about the same as yours - it looks like "roll your own" time.
The IPC::Sharable module basically serializes the shared variable, transports it, then re-creates it (with fancy locking and 2-way Ties). I don't see any way to avoid the serialization/re-assembly.
You could potentially re-design your app such that instead of exposing the data, you expose methods to manipulate the data. Then your problem comes down to (relatively) simple RPC.
"When you are faced with a dilemma, might as well make dilemmanade.
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.