On Nov 19, 2007 5:41 PM, Jeff Mesnil <[EMAIL PROTECTED]> wrote: > Hi Trustin,, > > Trustin Lee wrote: > > Hi folks, > > > > I've just succeeded to import AsyncWeb HTTP codec into > > mina-filter-codec-http submodule in trunk. I had to rewrite the > > client side codec, but it seems like it's working OK. Please note > > this is a massive change so you might see a lot of compilation errors > > if you were using the HTTP client codec in the trunk. The notable > > changes are mostly renaming: HttpProtocolCodecFactory -> > > HttpCodecFactory, HttpRequestMessage -> HttpRequest, > > HttpResponseMessage -> HttpResponse. You will also find subtle > > differences in message model, but it should be easy to follow up. > > I've tested the new code in mina-filter-codec-http & asyncweb-core and I > encountered a few problems: > > 1/ asyncweb-core does not compile because class HttpHeaderConstants > (from mina-filter-codec-http) is referenced by asyncweb-core's > AbstractHttpServiceContext but is not public (package visibility only) > > 2/ there is a "typo" in mina-filter-codec-http's HttpRequestDecoder: the > DecodingStateMachine to use is Http*Request*DecodingState, not > Http*Response*DecodingState
Oops! I am sorry about these silly problems. They were all fixed now. Just in case you are using the classes in AsyncWeb, you don't need to do that if you just want a simplistic HTTP client/server. > 3/ in the same state machine, the parameters of HTTP request are not > decoded (still figuring this one out though...) What HTTP method are you using? Thanks, Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
