This module looks promising. Thanks for providing the source - FYI - it compiled, installed and tested flawlessly on my XP machine using the dot net compiler.
I'm sure you are probably already considering providing an object-interface for this module - just in case you are not, let me be the first to whine on this subject... or even better - if I find time, I'll try to write an OO wrapper for this module. Let me know if your or anyone else has already started on such a persuit.
The Interface I'm thinking of would look like this:
my $MM = Win32::MMF->new("My (optional) Unique Namespace name");
# If unspecified, a new GUID would be used for namespace
# Fork the child here -- Parent & Child share $MM.
# In Parent ----
my $view = $MM->CreateView("Optional Unique Name");
my $err=$view->lock([$TIMEOUT]); # Optional, Prevent others from Writi
#--- In Child --
my $view = $MM->GetView("Optional Unique Name", \&$Optional_CallBack_R
# Line above blocks if callback is not specified
my $Data = $view->read();
"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 How to display code and escape characters
are good places to start.