On Wednesday, November 5, 2003, at 12:38 PM, James Lavery wrote:
The current prototype manages navigation around the site and choice of stylesheet, by processing the CGI submission events (using the CGI::XMLApplication Perl module) and then using Perl code called from the CGI script.
Using axkit one of the benefits you can get is a very good caching mechanism.
Does AxKit support user session/login management as part of its core functionality?
No.
With AxKit, how does one set up the basic stylesheet-selection mechanism? For example, if a user fills data on a page produced using stylesheet A, how to take the user to stylesheet B, displaying data produced from having queried the database using parameters supplied in stylesheet A. I presume that ultimately we're into HTML forms etc., or do I presume wrong?
If you mean XSLT stylesheets, then correct, HTML forms it is. AxKit doesn't supplant HTML .. it serves it ;-)
(Oh yes, and are people generally using XpathScript or XSL?)
Everyone uses XSLT :-D
simon
-- www.simonwoodside.com :: www.openict.net :: www.semacode.org 99% Devil, 1% Angel
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
