Fast enough :) Actually its quite peppy for what we're doing, though it does require a bit more memory, since all filter stages are kept in memory.
Generally we're bulk generating things that don't change, but for data lookups and things of that nature, its pretty easy to whip up an xml document and put some perl/ASP in it :) You can see our site at: http://icpac.indiana.edu. Its roughly 8600 xml files, 40 cgi scripts, and 15 asp pages. It works out to about 36000 distinct URLs, since most of the xml files can be viewed different ways by altering the Path info or adding .pdf as an extension... The server is a 2cpu 1.266GHz Pentium III with 2G of ram running Linux. We're having stability problems (not AxKit related...we went from 4M swap used to 512M in 5 minutes...) but I'm very happy with AxKit's performance. Of course, to fuel the _other_ thread, we're using XPS exclusively. :) Brian Wheeler [EMAIL PROTECTED] On Tue, 2003-02-04 at 10:20, Robin Berjon wrote: > brian wheeler wrote: > > On Tue, 2003-02-04 at 01:29, Kip Hampton wrote: > >>I personally favor using something like CGI::XMLApplication because the > >>model fits the way I like to work, but nothing that baroque is required. > >>Again, as long as it can return an XML document to the Provider when > >>needed, it can be as quick-hacky or as over-engineered as the situation > >>warrants. > > > > I've found that using Apache::RegistryFilter and Apache::ASP filtered > > into AxKit makes for neat fun. > > I'm curious as to the performance of that kind of setup, do you have any numbers? > > -- > Robin Berjon <[EMAIL PROTECTED]> > Research Engineer, Expway http://expway.fr/ > 7FC0 6F5F D864 EFB8 08CE 8E74 58E6 D5DB 4889 2488 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
