On Thu, 2002-10-10 at 14:43, Paul wrote: > > There's nothing you've mentioned so far that requires Java. It would > > be much faster to port it to FastCGI or the like. > > I just meant that iPlanet's internal API was probably going to require > Java or C, and not Perl.
FastCGI and PersistentPerl are both working equivalents to mod_perl with similar capabilities and performance. They should work just fine with iPlanet. > I can redo most of it as CGI if necessary, but > some of that will require slieght-of-code like embedding data in > cookies or hidden form elements I don't see why that would be any different from what you currently have. Any state mechanism requires cookies, URLs, or hidden form values for maintaining at least a unique ID on the client side. There is no other way to do it. > I just prefer having all the data from the engine available > from the request object, and I'm gonna miss that. Again, I don't understand what you think you're going to lose. All the basic data available under mod_perl is available under everything else as well, albeit with a slightly different API. - Perrin
