tags:

views:

2283

answers:

3

I need a byte buffer class in Java for single-threaded use. I should be able to insert data at the back of the buffer and read data at the front, with an amortized cost of O(1). The buffer should resize when it's full, rather than throw an exception or something.

I could write one myself, but I'd be very surprised if this didn't exist yet in a standard Java package, and if it doesn't, I'd expect it to exist in some well-tested public library.

What would you recommend?

+1  A: 

Not sure if it is "the best", but you have a nice example of Circular Byte buffer here.

Those Java Utilities - OstermillerUtils classes are under GPL license.

This Circular Byte Buffer implements the circular buffer producer/consumer model for bytes. Filling and emptying the buffer is done with standard Java InputStreams and OutputStreams.

Using this class is a simpler alternative to using a PipedInputStream and a PipedOutputStream.
PipedInputStreams and PipedOutputStreams don't support the mark operation, don't allow you to control buffer sizes that they use, and have a more complicated API that requires a instantiating two classes and connecting them.

VonC
That's not bad. It's not resizable, and it's GPL so you have to watch out for licensing issues but it would be a good start.
paxdiablo
Nice link (I found this too on google) but I can't use it, I absolutely need it to be nonblocking,therefore resizable. +1, but not answered :-)
Wouter Lievens
It has a private resize method that you can easily adapt to your dynamic resize need.
VonC
@Wouter, it will always be blocking at some point (if you can't allocate more memory for the bytes), so you'd have to code for that anyway.
paxdiablo
@Pax: you mean when you're out of memory? That line of thinking would go for any resizable container. Or am I misunderstanding?
Wouter Lievens
Not misunderstanding. I'm saying, since you have to code for a limit of some sort, it makes little difference between 100, 10,000 or the extent of memory (in terms of coding effort). Although I understand that resizable gives the best tradeoff between initial size and maximum capability.
paxdiablo
+1  A: 

I'm using a java.util.ArrayDeque<Byte> in a project with similar requirements. Note that you can easily change implementation using a java.util.concurrent Queue implementation.

dfa
You might find that using Byte instead of byte is a significant perform hit. ;)
Peter Lawrey
A: 

Another solution is to use GrowablePipedOutputStream and GrowablePipedInputStream by JBoss.

Mohsen