Arne, I find your tale somewhat interesting, and if it pleases the list, I think I'd like to see a short discussion on one of its topics. Perhaps the answer is obvious, and I have just not found the correct AxKit bits :-)
> I am admittedly an abnormal user of AxKit, spending a lot of time trying to > get it to work in a way it wasn't quite set up for. But my end goal is > simple: Separate Data, Business Logic and Presentation completely. This is all fine and dandy. I think we all would like to do this, in one way or another. If nothing else, but so that I can syntax check the logic with -c :-) However, HTTP being the wonderful thing that it is, things tend to go from bad to worse when it comes to actually handling form submissions and similar things. I guess one way of doing what I want to do is to create an XSP for every page that contains some kind of logic. Then have the XML contain a tag that calls that XSP, have the XSP do whatever magic is required, return some XML and then have XSL transform it. But creating so many XSPs sounds slightly insane, and it requires a httpd.conf tweak every time I make a new one. So the situation I'm in now is that I have a small mess of custom made XSPs which tie in with my pages together with AxKit::XSP::PerForm which does most of the bulk work surrounding forms. It works. But it's not pretty. -- Jonas �berg Systems administrator/webmaster, Department of Informatics, School of Economics and Commercial Law, Gothenburg University. Phone. +46-31-7732717, Fax. +47-31-7734754 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
