comment on

It isn't horrible, but it is an interface to the Apache library so there's a non-perl depdency there.

In the ideal case I'd be looking for Net::Master class, or similar, with helper classes for different transports. I've been sketching out a prototype using Net::Master::UDP just adding send/recv methods and keeping the logic in the main module, which seems like a good direction.

The biggest downside is that this is all async stuff, and I've little experience with perl and threading..

Update: I've got some simple code working for the case of UDP-broadcast only, using threads and threads::shared. I suspect this might be fragile, but I will see.

Steve
--

In reply to Re^2: Leader election in a distributed situation? by skx
in thread Leader election in a distributed situation? by skx

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> <u> <ul>
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 intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks