On Wednesday, 13. September 2006 19:39, Andrew Davies wrote: > Currently our site runs with AxKit 1, a mixture of static > XML->XSLT->HTML stuff with a pile of XSP thrown in for the dynamic > content. There's a bunch of homebrew taglibs (often ripping stuff from > mysql databases), and use of other tablibs such as PerForm, Param, > ESQL, Util, WebUtil etc etc. User authentication and session management > are built on Apache::AuthCookie and Apache::Session. > > Currently it isn't bust, so why should I try and fix it... well hey; > AxKit 2 is there so why not? > > So can anyone give some hints as to what I can expect to "just work" and > what else may involve pain? Am I right to be concerned about the user > and session stuff?
Right. I will write something, that's for sure, and I hope to get some type of session and auth plugin(s) into the core distribution, but it isn't done yet. Cookie support could be a bit rough, didn't use it yet (Matt knows the answer). And as Sebastian said, anything using $r will need to be ported. Usually, that's not a big issue, since most of the info is there, just somewhere else. Perhaps the only major functional difference between mod_perl and AxKit2 is the absence of subrequests. If you need them, feel free to speak about your requirements. On the other hand, XSLT, XSP and Taglibs should work. XSP hasn't seen much testing yet, expecially regarding the above mentioned porting issues in taglibs, but it should be fully functional, any bugs you find are just waiting to be fixed :) I wouldn't port big existing code bases over yet unless you have the time to report bugs and help testing new areas. If you have that time, be our guest :) -- CU Joerg --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
