Thanks, Craig.
> > I thought that defining interfaces (like ServletResponse) is good for
> > abstracting things and allowing developers to replace functionality. But in
> > this case abstraction gets meaningless.
> >
>
> The abstraction would be fine ... if your calling class did it's part of
> the bargain. But that means you have to act (from the perspective of the
> JSP page you're calling) like you are Tomcat.
Now I got the point, thanks.
> > Do you have any idea how to solve that?
> >
>
> A completely different strategy would be to have your extra thread do its
> computations and store the data to create the results into a session
> attribute. Then, when your user asked for the page to display the
> results, the calculations would have already been completed (or, if the
> attribute isn't there, you can display a "still working on it ..." page),
> the response can be displayed in the usual way.
Okay, I'll have to do it that way then.
Thanks a lot for your time.
Bye,
Levo.
--
Feature-IT Information Technology
eMail: [EMAIL PROTECTED]
http://www.feature-it.de (Deutsch)
http://www.feature-it.com (English)
Phone: +49 511 95981-0
Fax: +49 511 95981-40
