"David P. Caldwell" wrote:
>
> I'm looking at 2.3 Proposed Final Draft 2.
> ...
Since the container is the one handing out IOExceptions from
client streams, it already knows if there's a problem on
that end.
SRV.9.9.2 goes into detail on the semantics of exception
handling. If you want to argue that programming-by-init-file
is an ugly, ugly thing, then I won't disagree, but it seems
pretty clear what the container's responsibilities are.
> Clarifying the correct semantics would allow container authors
> to handle application-level failures one way and network-level
> failures another ...
>
What ways, exactly?
--
Christopher St. John [EMAIL PROTECTED]
DistribuTopia http://www.distributopia.com
___________________________________________________________________________
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
