Hi all,
I am using the Grizzly NIO framework along with the Grizzly HTTP Engine to
process incoming messages. My question is how do I get around the inherent
8K buffer limit for incoming messages?
Other posts I have read achieve this by directly coding to the buffer API
when people are creating their own protocol parsers, however, I am using
the Grizzly HTTP Engine and cannot see how to do this.
Surely the HTTP engine must (needs to) use some kind of expandable byte
buffer to cope with variable length messages in an efficient manner?
TIA, Mark
--
View this message in context: http://www.nabble.com/8K-buffer-limit-tp18922684p18922684.html
Sent from the Grizzly - Users mailing list archive at Nabble.com.