byte[] problem

Thread view:

Geez - 15 May 2005 21:02 GMT

Hello all,

I created a descriptor which contains of two parts:
1: header: fixed length
2: field: variable length

The field part will contain a list of files. Now from 1 to 22 files i got no
problems.
But at 23 files i have problems sending the descriptor after i created it.

descriptor: (22 files)
- length byte[] header: 19
- length byte[] field: 479

descriptor: (23 files)
- length byte[] header: 19
- length byte[] field: 499

What can i have done wrong? Any advice?

Greetings

Geez

Reply to this Message

Boudewijn Dijkstra - 15 May 2005 22:24 GMT

> Hello all,
>
[quoted text clipped - 9 lines]
> - length byte[] header: 19
> - length byte[] field: 479

19 + 479 < 512

> descriptor: (23 files)
> - length byte[] header: 19
> - length byte[] field: 499

19 + 499 > 512

> What can i have done wrong? Any advice?

Flush the stream.

Reply to this Message

Geez - 16 May 2005 08:43 GMT

Hallo Boudewijn,

Thanks for your reply, but i don't understand it well in fact.
What's so special about 512?

Greetings

Geez

Reply to this Message

Boudewijn Dijkstra - 16 May 2005 12:08 GMT

> Hallo Boudewijn,
>
> Thanks for your reply, but i don't understand it well in fact.
> What's so special about 512?

The default buffer size for a BufferedInputStream or a BufferedOutputStream is
512 bytes. A common mistake is forgetting that buffered streams don't
transfer their data immediately, but only in chunks of the buffer size or when
flushing it programmatically.

Reply to this Message

christopher@dailycrossword.com - 17 May 2005 03:12 GMT

You didn't really ask what's so special about 512, did you? Gee,
that's like not knowing phones used to have rotary dials, hence "dial a
phone". I'll bet you weren't alive when we landed on the moon, were
you . . .

Reply to this Message

byte[] problem

Free Magazines