Lists Home |
Date Index |
- From: "Clark C. Evans" <email@example.com>
- To: David Brownell <firstname.lastname@example.org>
- Date: Mon, 3 Jan 2000 09:52:43 -0500 (EST)
On Sun, 2 Jan 2000, David Brownell wrote:
> > -- you get a ZipException, presumably, because of an error
> > in the format of the zip file you're reading from;
> Curious example. java.util.zip.DataFormatException is what I'd
> expect to get when faced with bad ZIP data. (Recalling some of
> the chaos involved in seeing JDK 1.1 get ZIP/JAR support, it's
> no surprise that its exception architecture seems pretty odd.)
> That's not an IOException.
I don't think it is all that cut and dry.
Let's say that you are reading information
from a TCP/IP pipe. And that, according to
the protocol, the next token arriving should
be an X. Now suppose that a Y arrives
instead. Is this an IOException?
Suppose instead that the file system directory
says that file FILE is N bytes long. Also
suppose, that the file system uses the token
X to mark the end of a file. Now, let's say
that while reading FILE from the hard drive,
token Y was found at position N instead of X.
Is this an IOException?
I guess I'm trying to say that a data format
exception in one context could easily be seen
as an I/O exception in another context.
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)