On Tue, Feb 17, 2009 at 12:07 PM, wrote:
> IMO, the perl threads sharing mechanism is flawed because
> (in my short experience with it) it does not allow certain
> interesting items (e.g. tied) to be shared.
Well, since everything shared by IPC::MMA has to go through Storable,
it has limitations
IMO, the perl threads sharing mechanism is flawed because
(in my short experience with it) it does not allow certain
interesting items (e.g. tied) to be shared. I hope that
if Perl 6 is ever released it will have a better threading
component.
w/r/t "figuring out itself", in looking at the code i
valerio crini schrieb:
Hi, I was wondering if is possible using same mod_perl handler
with different ports and how can i manage to configure it.
so if i call http://../query:12200 i call Handler
and if i call http://../query:12300 i call Handler2
This, of course, would not be read as a port
On Tue, 17 Feb 2009 16:20:42 +0100
valerio wrote:
> Hi, I was wondering if is possible using same mod_perl handler with
> different ports and how can i manage to configure it.
The Listen directive is part of the server configuration, and not valid
within a Location block. Configure your server
Hi, I was wondering if is possible using same mod_perl handler with
different ports and how can i manage to configure it.
I was thinking of a similar thing:
SetHandlerperl-script
Listen 12200
PerlResponseHandlerHandler
SetHandlerperl-script
PerlResponseHandlerH
On Tue, Feb 17, 2009 at 8:13 AM, André Warnier wrote:
> Now, how about extending this so it would work on both Unix/Linux *and*
> Windows platforms, figuring out itself where it is and doing whatever is
> needed to use the OS mechanisms available ?
The underlying library does not support Windows:
cr...@animalhead.com wrote:
I would like to thank the people on this list who helped me get
my new CPAN module IPC::MMA up and running. Without
volunteers like those in this community, the technical world
would be a much poorer place.
If anyone would like to read the docs and/or try the module,
