Re: java.io.File to java.lang.String

From:

Patricia Shanahan <pats@acm.org>

Newsgroups:

comp.lang.java.programmer

Date:

Wed, 04 Jul 2007 08:54:21 -0700

Message-ID:

<f6gfrf$4q8$1@ihnp4.ucsd.edu>

Jeff Higgins wrote:

Esmond Pitt wrote:

Jeff Higgins wrote:

Again, I'm sorry but I haven't been able to figure out what might
cause read(charBuffer) to not read all that could be read?

The fact that the Javadoc specifically says so?

:-) Yup, it is what it is.
Better for me to focus on what rather than why.

I think the "why" is because part of the file may be buffered in memory.
Disk reads are always in fixed block sizes, and the data required to
fill the program buffer may cross block boundaries.

Suppose some, but not all, of the data for the read call is already in
memory. The system could make you wait many milliseconds for a physical
read to let it fill your buffer. It is often more efficient to let you
get on with processing the data that is already available, in parallel
with a physical read to get more data. For example, the read call may be
being issued by a BufferedReader doing a readLine, and it can return
data to its caller as soon as it has a whole line.

Patricia