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 the serialization requirement as i'm dealing with perl
>encapsulated
> modperl> c++ objects...
>
> sorry to respond to myself but i just realized a got momentarily confused.
> what i would love to have is
>
> api consistent (w/ IIS/ASP) means of all scripts served by apache
> process "foo" to be able to access the $Application data and that
> this data doesn't have a must-be-serializable requirement.
>
> Apache::ASP currently provides
>
To really have a consistent API, Apache + mod_perl will have
to go multi-threaded. Or you can turn off $Application with
AllowApplicationState 0 as I suggested in the last mail, and
run your Apache web server with MaxClients 1, and put a proxy
in front of it. I wouldn't advise it, but its a possibility.
Note that if you do go the route of disabling $Application
and such, you will lose access to the events Application_OnStart
& Application_OnEnd
-- Joshua
_________________________________________________________________
Joshua Chamas Chamas Enterprises Inc.
NodeWorks >> free web link monitoring Huntington Beach, CA USA
http://www.nodeworks.com 1-714-625-4051
