Thanks Alexey,
On Wed, Apr 1, 2009 at 7:53 PM, Oleksiy Stashok <Oleksiy.Stashok_at_sun.com>wrote:
> Hi John,
>
>
>
>
> 3) other?
>>
>
> If the header has always fixed size (let's say N bytes) - probably it could
> make sense to reserve in user data buffer first N bytes. So, once userdata
> will be ready - you can prepend header to existing buffer.
>
> Does it make sense?
>
Well, I don't have much flexibility at the higher level, either. I'm using
grizzly as a replacement for a socket implementation of another open source
project. So, either I open the guts of grizzly or the guts of the higher
level project, getting messy either way. After getting messy, and looking
back at what I'd done, I'd think a grizzly with multiple ByteBuffer support
would be generally more useful.
>
> WBR,
> Alexey.
>
>
>
>>
>> Regards,
>> John
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
>