Joel Reed wrote:
>
> modperl> yes this is the killer with making my stuff work for both iis/asp & modperl.
> modperl> do you have any suggestions for an api consistent solution? maybe i could
> modperl> hack up something where $Application data was obtainable thru IPC? the
> modperl> killer is th
On Mar 29, [EMAIL PROTECTED] hacked the bitstream to say...
modperl> Joshua> What you don't get here is interprocess communication
modperl> Joshua> which is what the use of $Application is geared for, that
modperl> Joshua> the data is stored is some process neutral location, so
modperl> Joshua> we
On Mar 29, [EMAIL PROTECTED] hacked the bitstream to say...
Joshua> Joel Reed wrote:
Joshua> >
Joshua> > this may be a dumb patch to Apache::ASP (at least it is my first).
Joshua> >
Joshua> > Rationale:
Joshua> >
Joshua> > i have the following issues with the current implementation of $Applicat
Joel Reed wrote:
>
> this may be a dumb patch to Apache::ASP (at least it is my first).
>
> Rationale:
>
> i have the following issues with the current implementation of $Application
>
> 1. everything you store in $Application->{foo} must be
> serializable my MLDBM. (right?) i
this may be a dumb patch to Apache::ASP (at least it is my first).
Rationale:
i have the following issues with the current implementation of $Application
1. everything you store in $Application->{foo} must be
serializable my MLDBM. (right?) i have SWIG'd c++ classes for
