Well, google came up with SPDY as an alternative to http for its data centers and we support that protocol...so I would suggest taking a look at leveraging that if you can and if that is enough benefit. Jetty 9 has been designed to separate protocol from semantic so as to better support modern protocols like SPDY and the forthcoming http/2.0 (which is also based on spdy). Not to mention our websocket support as well... So yes, we should be able to support additional protocols as desired. Is this something you guys want to tackle or is it work you are looking for us to take on? We have done sponsored development work in the past through our professional services side through Intalio/Webtide. If you are interested in that let me know.
cheers, jesse -- jesse mcconnell [email protected] On Tue, May 21, 2013 at 5:36 PM, ccleve <[email protected]> wrote: > We use Jetty to communicate via http with the outside world. For > high-speed communication within our cluster, though, we're considering > something without the overhead of http, something like Thrift or Protocol > buffers. > > Is it possible to implement these things in Jetty itself? Is there some > place to insert a lower-level handler? We really don't want to give up all > of Jetty's cool asynchronous NIO stuff. > > We'd also rather not switch to Netty to make this work. > > ______________________________**_________________ > jetty-users mailing list > [email protected] > https://dev.eclipse.org/**mailman/listinfo/jetty-users<https://dev.eclipse.org/mailman/listinfo/jetty-users> >
_______________________________________________ jetty-users mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/jetty-users
