On Thu, 16 Sep 1999, Rogatkin, Dmitry M wrote:
> > Yes, calling super.service() will perform the conditional GET
> > support, but it will also do everything else it already does,
> > including call your doGet()/doPost()/etc. method.
> >
> > If you call super.service() at the beginning of your override
> > method, by the time it returns, the request has been processed,
> > and the response has been created. If you wait and call
> > super.service() after you have already prepared the response, the
> > doGet()/doPost() method that is called will run into problems
> > trying to acquire a ServletOutputStream or PrintWriter, because
> > you already grabbed them.
> >
> > What's left for your overriding service() method to do, unless all
> > you want is to count hits or something innocuous like that?
>
> It's too obvious. A calling super method should be conditional. You
> also can provide flags, which say should called doGet/doPost do
> something, or just return control. But, I couldn't agree it requires
> some programming efforts, when someethig is bad designed.
Wait, wasn't simplicity an issue when we started this discussion?
(That's a rhetorical question.)
Milt Epstein
Research Programmer
Software/Systems Development Group
Computing and Communications Services Office (CCSO)
University of Illinois at Urbana-Champaign (UIUC)
[EMAIL PROTECTED]
___________________________________________________________________________
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff SERVLET-INTEREST".
Archives: http://archives.java.sun.com/archives/servlet-interest.html
Resources: http://java.sun.com/products/servlet/external-resources.html
LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
