On Mon, 6 Aug 2001, Erik Weber wrote:
> This is a good discussion.
>
> I would like to introduce the question: How much work is it to undo
> the platform dependency,
How does one do this without insisting that all containers implement the
same APIs with the same behavior?
Oh, yeah, it's already been done in 2.3 with application event
listeners. :-)
> and is it worth the liability to take
> advantage of a nice feature of the server?
>
That's always a "risk versus reward" tradeoff. If I were a malicious
platform vendor, I'd do everything I could to encourage you to utilize my
platform specific stuff and get locked in.
On the other hand, I might be very customer-sensitive and want to provide
you a bunch of cool features above and beyond the spec so that you can be
productive ... but they only work on my platform.
Whether it's worth the risk or not is totally up to you ... there's no pat
answer.
> Specifically, would the interceptor approach offer significant
> benefits over the Servlet adapter approach? And how much work would it
> involve (potentially) to adapt the interceptor approach to some other
> unnamed platform if needed?
>
If the "unnamed platform" is open source, you could theoretically do this.
If not, are you planning to decompile the bytecodes so that you see how it
works, and then figure out how to hack the insides to use your additional
functions?
The only way to rely on a platform-independent feature is to have it in
the spec.
> -Erik
>
Craig
>
>
> "Pier P. Fumagalli" wrote:
>
> > Filip Hanik at [EMAIL PROTECTED] wrote:
> >
> > > For Tomcat 3.x, you can create an interceptor to act as a startup class.
> > > you can just configure it using the server.xml file, read more about this in
> > > http://www.filip.net/tomcatbook/TomcatInterceptors.html
> >
> > Again, this would be unportable to other containers... My reasoning is that
> > Erik needs some functionality for a web application that will allow his code
> > to be 100% portable on all possible servlet containers.
> >
> > Using tomcat interceptors is exactly like using Weblogic's startup classes,
> > unportable. That's why I'm not a fan of interceptors (or valves in Tomcat
> > 4.0), or ANY other unportable feature.
> >
> > Pier
>
>
