[CONF] Apache MINA > MINA 3.0 HTTP Codec

[confluence]

MINA 3.0 HTTP Codec Page edited by Julien Vermillard Changes (5) ... I started this project because I needed a well know codec for testing MINA 3.0 ideas and because I needed some "Lego" bricks for building very specialized HTTP servers and proxy. The goal of the mina-http module is to provide : - a low level codec for encoding/decoding HTTP request, response and body element. - the plumber for building HTTP server or client easily. ... h1. HTTP elements HTTP is quite a simple protocol : a HTTP client send a HTTP request to the server and it replies with a HTTP response. A HTTP client send a HTTP request to the server and it replies with a HTTP response. It It's often modelled ( in AsyncWeb, Deft and javax.servlet API) using a HttpRequest and a HttpResponse object. It's a good idea until you want to send big body contents (in HTTP request post/put or in HTTP response). For example in Asyncweb you are doomed to create te whole HTTP object in memory. the same problem occurs with streaming and Comet style server. It's a good idea until you want to send small body contents (in HTTP request post/put or in HTTP response). For example in Asyncweb if you want to send a large document you are doomed to create the whole HTTP object containing the big document in memory. The same problem occurs with streaming and Comet style server. For solving that the servlet API expose an old fashioned OutpuStream for writing your contents. It's not compatible with NIO ByteBuffer so you need to use plain old byte arrays and you can't achieve zero copy. That why in MINA 3.0 HTTP codec the elements and splitted a stream of different class. ... Full Content Key ideas I started this project because I needed a well know codec for testing MINA 3.0 ideas and because I needed some "Lego" bricks for building very specialized HTTP servers and proxy. The goal of the mina-http module is to provide : a low level codec for encoding/decoding HTTP request, response and body element. the plumber for building HTTP server or client easily. a simple HTTP server and a simple HTTP client for benchmarking MINA 3.0 I/O processing What is not going to be A full feature web client/server like AsyncWeb, Deft, Apache HC nor a web servlet container but it can be a basis for building all this kind of project. HTTP elements HTTP is quite a simple protocol : a HTTP client send a HTTP request to the server and it replies with a HTTP response. It's often modelled ( in AsyncWeb, Deft and javax.servlet API) using a HttpRequest and a HttpResponse object. It's a good idea until you want to send small body contents (in HTTP request post/put or in HTTP response). For example in Asyncweb if you want to send a large document you are doomed to create the whole HTTP object containing the big document in memory. The same problem occurs with streaming and Comet style server. For solving that the servlet API expose an old fashioned OutpuStream for writing your contents. It's not compatible with NIO ByteBuffer so you need to use plain old byte arrays and you can't achieve zero copy. That why in MINA 3.0 HTTP codec the elements and splitted a stream of different class. For HTTP Response : an HttpResponse, followed 0..N ByteBuffer compounding the body and a HttpEndOfBody marking the end of the HTTP response. For HTTP Request : an HttpRequest, and if it's a POST or PUT : 0..N ByteBuffer compounding the body and a HttpEndOfBody. How an HTTP Request is decoded to different slice for easier processing Change Notification Preferences View Online | View Changes | Add Comment