RE: [Mimedefang] Embedded perl

2004-04-24 Thread David F. Skoll
On Sat, 24 Apr 2004, Les Mikesell wrote:

> Would you have a lot of unnecessary overhead if, instead of
> writing your own multiplexing and embedded perl, you ran
> a stock apache/mod_perl or fastcgi and a really simple
> front end that dispatches the jobs via http requests?

I have no idea, and I have no inclination to find out. :-)

> It would add some software dependencies, but all things
> that are well tested, packaged in distributions, and
> already understood by system administrators.

apache + mod_perl is a very fragile thing, IMO.  There are lots of
things still broken in apache2's mod_perl.

> You would also inherit a framework for web status checking and
> administration.

We already have that in our commercial product using the multiplexor
control socket and other means, so it's already doable.

Regards,

David.
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang


Re: [Mimedefang] Embedded perl

2004-04-24 Thread David Eisner


On Fri, 23 Apr 2004, David F. Skoll wrote:
> On Fri, 23 Apr 2004, Henrik Schmiediche wrote:
> > What is the advantage to Embedding Perl in the muliplexor?
>
> Faster startup time and much less memory use.


The man mimedefang-multiplexor man page says:

  -E   Specifies that the multiplexor should create an embedded Perl
   interpreter.  This can improve performance dramatically.  But
   see the section "EMBEDDING PERL" for more information.

When I read this it wasn't clear whether "performance" applied only to
speed, or to memory use, or to both.  Perhaps the second sentence should
be "This can dramatically decrease both startup time and memory use."

Just a thought.

-David

___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang


RE: [Mimedefang] Embedded perl

2004-04-24 Thread Les Mikesell
On Sat, 2004-04-24 at 09:10, David F. Skoll wrote:

> Yes; you need either a shared library libperl.so, or a static one (libperl.a)
> on your system.

Would you have a lot of unnecessary overhead if, instead of
writing your own multiplexing and embedded perl, you ran
a stock apache/mod_perl or fastcgi and a really simple
front end that dispatches the jobs via http requests?
It would add some software dependencies, but all things
that are well tested, packaged in distributions, and
already understood by system administrators.  You would
also inherit a framework for web status checking and
administration.

---
  Les Mikesell
   [EMAIL PROTECTED]


___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang


RE: [Mimedefang] Embedded perl

2004-04-24 Thread David F. Skoll
On Fri, 23 Apr 2004, Henrik Schmiediche wrote:

> How can you test if a given implementation is safe?

Look at "configure.in" and search for
"AC_MSG_CHECKING([if it is safe to destroy and recreate a Perl interpreter])"

> Does Perl need to be compiled in any special way to enable embedded Perl to
> work?

Yes; you need either a shared library libperl.so, or a static one (libperl.a)
on your system.

Regards,

David.
___
Visit http://www.mimedefang.org and http://www.canit.ca
MIMEDefang mailing list
[EMAIL PROTECTED]
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang