BufferedReader.readLine() slow reading long line.

[sumarlidason]

Good Afternoon,

I am interfacing with a web site using their XML API to retrieve data. Unfortunately - everything is coming down the pipe on a single line, and the code I'm using is text book - I think.

BufferedReader d = new BufferedReader(new InputStreamReader(urlConn.getInputStream()));
String output = d.readLine();

In some instances readLine() takes 22 seconds to execute, there must be a better way.

Any ideas would be appreciated! :)

[Norm]

everything is coming down the pipe on a single line

Is 22 seconds a reasonable time for the number of bytes being read?

[sumarlidason]

Yes, that is a good point. :)

I should have included that my goal was to show progress to the end user instead of one of those never ending progress bars.

Also,
urlConn.getContentLength() returned unknown length, so If i can't get the content size all of this is moot anyway. Is there another way to retrieve the size of the content?

[Norm]

Have the sender send the length.

[sumarlidason]

Lets say I could make that happen; I'd like a way to read ?2048? bytes from the stream at a time, then I could provide a pretty accurate progress bar for the end user.

[Norm]

I'd like a way to read ?2048? bytes

Look at the read() methods.

[sumarlidason]

Look at the read() methods.

At first glance I thought that was my answer, but the implementation is a little different, the parameter off,

off - Offset at which to start storing characters

looks to be used as an offset into the char[] you supply, not an offset into the BufferedReader. The other read() only reads a single byte, and this doesn't seem like a good idea for several MB of data.

Thank you for helping me.

[sumarlidason]

Or - the buffered reader handles that internally like it does with read(). I'll give that a shot.

[Norm]

Also look at the Reader class that BufferedReader extends.

[sumarlidason]

It works, but not as I expected. BufferedReader::read() stops way before 2048. According to the docs it stops for only these reasons,

The specified number of characters have been read,
The read method of the underlying stream returns -1, indicating end-of-file, or
The ready method of the underlying stream returns false, indicating that further input requests would block.

1) condition not satisfied
2) condition not satisfied
3) doubtful with my 127 byte test message

Alas, I think I can work with it, thanks!