----------------------------------------------------
Please read the FAQ at <http://java.apache.org/faq/>
It has a search feature and all the answers!
----------------------------------------------------
> Servlet chaining allow you to drop the thread of the previous servlet and
> having a new one starting to handle the next step which could be formatting
> the response according to a device.
So, why not do that within your code? Why hack the server to do such a
thing?
> Anyhow is there a place talking about
> why it is a bad idea and how to design a solution to solve the same type of
> problem.
[EMAIL PROTECTED]
> By the way I already looked at the FAQ, and I didn't find there a
> satisfactory answer to this question.
Oh gee, I'm sorry that it wasn't satisfactory for you. Gezz...
> Stating that it is not part of the API and therefore not good is a little
> bit too simplistic as an explanation for me. Especially when you see that
> most servers are implementing this feature. Are we the only one right
> against the rest of the world again?
Most servers are commercial and are at the whim of paying customers that
aren't intellingent to realize that it is a bad solution and force them to
implement a bad design that isn't even in the servlet spec. On top of it,
they have rooms full of people who sit there all day long and answer idiodic
questions about how to setup such a configuration because it is to confusing
for their customers to understand. As an open source project we are not
(un)fortunate enough to have such plentiful resources. ;-) Of course that
isn't the only excuse...
Answer my question above about why you can't just write your code to do what
you want instead of hacking the server to do it for you? What is wrong with
using Class.forName() to do the EXACT same thing? Not only do you have more
control, but it is within the logic of your servlet instead of the servlet
engine and you can do more than just chaining based on content-type.
I have personally done a framework that allows for this type of design and
works wonderfully...<http://www.working-dogs.com/dash/>
Lastly, Craig has come up with a better design (pipes) that will hopefully
make it into the next generation of servlet engines produced by the Jakarta
group. You can view the source by checking out the 1_1 branch in CVS.
-jon
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
