Niclas,
Performance is our main concern. I have not tested this out yet but I would
venture a guess that we would have scaleability issues if we were running
everything through the JSSI servlet instead of using the built in stuff that
is part of Apache.. We have some custom ad serving SSI that would somehow
need be merged with the JSSI module as well and I don't know what that would
entail at this point.
I am new to this SSI game so please bear with me. <sheepish grin>
--sean
http://www/tripod.com
Niclas Hedhman wrote:
> What happens if you
> ApJServAction .html /servlets/org.apache.ssi.SSIServlet
> ??
> Is there any conflicts, beside performance? Should not be, should there?
>
> Niclas
>
> Sean Shanny wrote:
>
> > To all,
> >
> > My Apache ignorance will show here. :-(
> >
> > We want to use the JSSI servlet with our Apache server but we do not
> > want to force users to change their file extensions to .jhtml. We have
> > other SSI stuff in our current Apache mod_include file and I was
> > wondering if it is possible to add the JSSI stuff as well so that the
> > page parser can call the appropriate 'stuff' when it comes across the
> > <servlet> tags?
> >
> > This way we could keep the generic .html extension yet have the
> > functionality of the JSSI.
> >
> > Thanks.
> >
> > Sean Shanny
> > Tripod, Inc
> >
> > ------------------------------------------------------------
> > To subscribe: [EMAIL PROTECTED]
> > To unsubscribe: [EMAIL PROTECTED]
> > Problems?: [EMAIL PROTECTED]
>
> ------------------------------------------------------------
> To subscribe: [EMAIL PROTECTED]
> To unsubscribe: [EMAIL PROTECTED]
> Problems?: [EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
