Re: PPerl

[Miroslav Madzarevic]

PPerl is written in C and from a superficial look at the source code I'd say it's not 
very difficult to understand.
If you want a pure perl solution take a look at POE (its being worked on ithreads 
these days but can use event
driven fork) or consider writing something yourself. I guess the whole idea is in 
using socets and selects for 
waiting and then using eval on your end code.
-- 
Regards,

   mire

perl -Mstrict -e 'print pack(h*, d69627560496e616d656e236f6d6),\n'

RE: PPerl

[Matt Sergeant]

 -Original Message-
 From: Miroslav Madzarevic [mailto:[EMAIL PROTECTED]]
 
 PPerl is written in C and from a superficial look at the 
 source code I'd say it's not very difficult to understand.

The stub is written in C. That's the point. You need a very fast, light C
stub, because the time is taken up by compiling the perl code, not in
forking these days.

 If you want a pure perl solution take a look at POE (its 
 being worked on ithreads these days but can use event
 driven fork) or consider writing something yourself.

Doesn't help. You still need something to call into your daemon. If that's
perl code you're going to have similar (though not necessarily identical)
slow startup problems.

(note that I think POE is great, but it's the wrong solution here)

Matt.

_
This message has been checked for all known viruses by Star Internet
delivered through the MessageLabs Virus Scanning Service. For further
information visit http://www.star.net.uk/stats.asp or alternatively call
Star Internet for details on the Virus Scanning Service.