On 8/8/06 14:56, "Matt Sergeant" <[EMAIL PROTECTED]> wrote:
> On 8-Aug-06, at 5:38 AM, Stuart Brown wrote: > >> I have one question which sort of relates; we've developed a tag >> library for >> AxKit / mod_perl over the last 3 years the provides the core >> functionality >> of all our web apps, I'm curious about the compatibility of our taglib >> architecture. > > Is this XSP taglibs? They will work out of the box (only I haven't > ported that functionality yet). If they're XSLT-style taglibs yes I'm > sure those will work too. The big change will be that you will have > to write new config files, and maybe some very small plugins to hang > everything together. I can certainly help you with that if you post > some of your current config. As far as our usage of AxKit1 goes we have a taglib written for mod_perl that uses TaglibHelper offer its functionality within our xsp pages. These xsp pages then follow a xsl pipeline that delivers the final mark-up. AxKit holds the whole thing together for us. > >> I read on a previous post that you can sit AxKit2 behind mod_perl and >> Apache, but will this be the best way migrate our setup? Apologies my >> Apache2, mod_perl2 knowledge is non existent at present. > > The answer is "it depends" :-) What do you do currently? Do you have > a front-end proxy? Currently we have a number of app servers running AxKit/mod_perl that back onto our Database proxy to deliver our dynamic content, our web proxy is under used at the mo. We could easily re-arrange so that AxKit sits on the proxy in front of mod_perl if that's what's required... In a nut shell I'd love to go down the route of a small lightweight server. Given our current usage of AxKit1 I thought I'd get some thoughts on how/if a similar setup will be possible with AxKit2, or if to get the advantage AxKit2 offers we will have to do things differently. > > Matt. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
