<div>> One option we have is to have "packet_worker_runner" as installed executable when user installs packet gem.</div>
<div> </div>
<div>The more I think about the idea of a packet runner, the more I like it.</div>
<div> </div>
<div>One reason I like it: it solves a problem with the Windows port I wrote. The Windows implementation needs to know what process to launch to create a new worker. It currently relaunches PACKET_APP, but I was concerned that might be a misuse of PACKET_APP and it forces the author of a PACKET_APP to implement code like what I wrote in script/backgroundrb to handle a "worker parameter. If there's a separate app whose only purpose in life is to be the runner, no one else has to write code to handle those parameters.</div>
<div> </div>
<div>- Brian<br><br></div>
<div class="gmail_quote">On Sun, Apr 13, 2008 at 6:53 PM, hemant kumar <<a href="mailto:gethemant@gmail.com">gethemant@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">
<div>
<div></div>
<div class="Wj3C7c"><br>On Sun, 2008-04-13 at 16:41 -0700, Paul Kmiec wrote:<br>> > This help significantly in improving stability of<br>> BackgrounDRb and code<br>> > written on top of packet. So what you guys think? Shall we<br>
> go for this<br>> > change?<br>><br>> It sounds good to me. Anything that helps stability and<br>> improves<br>> memory usage will always get my vote.<br>><br>
> I agree.<br>><br>> Paul<br><br></div></div>Okay folks,<br><br>I have updated git repo of just packet with latest changes wherein<br>I have removed fork in favour of fork and exec:<br><br><a href="http://github.com/gnufied/packet/tree/master" target="_blank">http://github.com/gnufied/packet/tree/master</a><br>
<br>The only catch is, now we need some kinda runner to run our workers<br>since exec takes argument in form of string only. For example:<br><br> exec "packet_worker_runner ##{t_worker_name}:{worker_read_end.fileno}:#{worker_write_end.fileno}:#{option_dump_length}"<br>
<br>One option we have is to have "packet_worker_runner" as installed executable when user installs packet gem.<br><br>Any other ideas?<br>
<div>
<div></div>
<div class="Wj3C7c"><br><br><br>_______________________________________________<br>Backgroundrb-devel mailing list<br><a href="mailto:Backgroundrb-devel@rubyforge.org">Backgroundrb-devel@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/backgroundrb-devel" target="_blank">http://rubyforge.org/mailman/listinfo/backgroundrb-devel</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Brian