|Re: [jetty-users] ByteBuffers and Jetty?|
Jetty's DefaultServlet is already doing a bunch of smart things
On Sun, Apr 29, 2012 at 04:15, David Walend <david@xxxxxxxxxx> wrote:
> I'm working on a project where I need direct access to memory via ByteBuffers and the ability to use http protocols to push the data around the internet. Can Jetty do that? How hard is it to do?
> (An early aspect of this project is transferring ~10GB files. Does Jetty have any baked-in limits on size of a single transfer?)
> I haven't been able to find doc or an email thread on ByteBuffers, so a "go read this" answer would be great help. Heck, even "go read this part of the source code" would be fine.
related to mapped file buffers and such, see
(in particular parameter "useFileMappedBuffer").
If that's not enough, you need to be more explicit on what you want to do.
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless. Victoria Livschitz
jetty-users mailing list