The main scalability constraints I am finding are:
1) Performance - from benchmarks and real world testing approx 100 requests per second give or take is the mean. From what I've read Axkit has much greater throughput.
This depends on a number of things. If your content is dynamic but cacheable, AxKit can get speeds circa 80% of raw Apache when the cache is hit. Beyond that, the speed depends mostly on which option(s) you pick. Eg. XML -> XSLT is blazingly fast, but you don't have access to the full gamut of dynamicity.
2) Extensibility - Mason is a nice app server package but some parts of it (i.e. error handling) have become intimately tied to the Mason structure in the latest branch. Also most of Mason's functions are tied to a request, so if I want to manipulate a template from within perl-space (i.e. on a cron basis have a script evaluate a template's contents) I have to generate a request object and component stack. I'm hoping that will be simpler with axkit.
AxKit sure is extensible, perhaps a little too much ;) You can pretty much replace any component with something that better suits your needs. Note however that, AxKit being a web publishing engine, some parts are tied to being used in web situations.
-- 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]
