-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday 13 May 2002 4:44 am, Steve Willer wrote: > On Mon, 13 May 2002, Christian Jaeger wrote: > > I know from some own experience that standard perl doesn't accept > > multiple interpreters in the same process, regardless whether a > > shared libperl is used. You have to compile perl with an option to > > enable multiple interpreters (something in the same direction as > > multithreading) and then explicitely create a new interpreter and > > switch contexts as described in perlembed. But I don't know whether > > you would need a separate interpreter anyway, why not load the custom > > stuff into the same? (apart from my above concern) > > One way to fix this would be to implement AxKit as a FastCGI server, or > something similar. I've always admired the FastCGI architecture by far. > > The only drawback with FastCGI at this point is that you don't get all of > the flexibility of being able to overload any or all of the request > processing steps. You can't implement a PerlTransHandler with it, for > example, although AxKit doesn't use that right now anyway.
Or PPerl. By using PPerl and a custom Apache handler we could get all of the benefits of FastCGI, and none of the drawbacks. - -- <:->get a SMart net</:-> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE831rZVBc71ct6OywRAmHNAKCFXNBnSGM8e3SUvZDBJNl9WLuKZACgwCzR CPncfdiVxQEkmafdX5a2A/k= =BHaj -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
