Re: mina-protocol-http-client, AsyncWeb and Jakarta HttpComponents
Hello Trustin, re-inventing the wheel is never a good thing. To me, it sounds reasonable that HttpComponents and MINA cooperate on the client side, at least for the higher level functionality. There is of course some kind of competition on the lower levels, where HttpNIO and MINA address similar functionality. IIRC, Oleg had slightly different design goals for HttpNIO. At the same time, he made sure that MINA can be used to implement the HttpNIO API. So yes, I can see potential for joined efforts: higher-level client functionality like HttpAuth and HttpCookie, and also a low-level component HttpNIO-on-MINA. But since Java NIO is not within my sphere of interest, I have to leave it to others to figure this out (or not). cheers, Roland
Re: mina-protocol-http-client, AsyncWeb and Jakarta HttpComponents
Hello Roland, Thanks for the response. Let's wait and see how people think about this issue. Probably Jeff will also have something to say. :) Cheers, Trustin On Nov 23, 2007 3:06 AM, Roland Weber [EMAIL PROTECTED] wrote: Hello Trustin, re-inventing the wheel is never a good thing. To me, it sounds reasonable that HttpComponents and MINA cooperate on the client side, at least for the higher level functionality. There is of course some kind of competition on the lower levels, where HttpNIO and MINA address similar functionality. IIRC, Oleg had slightly different design goals for HttpNIO. At the same time, he made sure that MINA can be used to implement the HttpNIO API. So yes, I can see potential for joined efforts: higher-level client functionality like HttpAuth and HttpCookie, and also a low-level component HttpNIO-on-MINA. But since Java NIO is not within my sphere of interest, I have to leave it to others to figure this out (or not). cheers, Roland -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
Re: mina-protocol-http-client, AsyncWeb and Jakarta HttpComponents
Trustin Lee wrote: 2) I also think mina-protocol-http-client module needs more work to provide enough features to compare with existing HTTP client libraries such as Jakarta HttpComponents, so moving it into sandbox might be a better solution considering that we are going to release MINA 2.0.0-M1 soon and we don't want to release unfinished module. It also might be the best idea to cooperate with HttpComponents team to make our current HTTP codec (i.e. mina-filter-codec-http) and mina-core plug into HttpComponents NIO extension very easily. I'd like to know what the HttpComponents team think about this issue. Trustin, I have a lot more code to contribute in this area as it is currently here: http://svn.apache.org/repos/asf/geronimo/sandbox/AsyncHttpClient This version contains authentication for Basic, Digest, and NTLM and is much more robust. I am currently working on connection reuse and caching and pooling for those HTTP/1.1 connections that support keep-alives. I am also working on allowing the NIO socket level attributes to be set as well as client SSL certificate authentication and Proxy Auth capabilities. Jeff Trustin
Re: mina-protocol-http-client, AsyncWeb and Jakarta HttpComponents
Whoops and forgot to mention...this version also has response timeouts working as well. Jeff Jeff Genender wrote: Trustin Lee wrote: 2) I also think mina-protocol-http-client module needs more work to provide enough features to compare with existing HTTP client libraries such as Jakarta HttpComponents, so moving it into sandbox might be a better solution considering that we are going to release MINA 2.0.0-M1 soon and we don't want to release unfinished module. It also might be the best idea to cooperate with HttpComponents team to make our current HTTP codec (i.e. mina-filter-codec-http) and mina-core plug into HttpComponents NIO extension very easily. I'd like to know what the HttpComponents team think about this issue. Trustin, I have a lot more code to contribute in this area as it is currently here: http://svn.apache.org/repos/asf/geronimo/sandbox/AsyncHttpClient This version contains authentication for Basic, Digest, and NTLM and is much more robust. I am currently working on connection reuse and caching and pooling for those HTTP/1.1 connections that support keep-alives. I am also working on allowing the NIO socket level attributes to be set as well as client SSL certificate authentication and Proxy Auth capabilities. Jeff Trustin
mina-protocol-http-client, AsyncWeb and Jakarta HttpComponents
Hi, I'd like to discuss 2 ideas in this post. (Apologies for cross-posting ;) 1) What do you think about merging existing mina-protocol-http-client module into asyncweb? Then AsyncWeb could be a one stop solution for HTTP client-server communication. Now the codec is separated from them into mina-filter-codec-http module, so the number of classes are pretty small. 2) I also think mina-protocol-http-client module needs more work to provide enough features to compare with existing HTTP client libraries such as Jakarta HttpComponents, so moving it into sandbox might be a better solution considering that we are going to release MINA 2.0.0-M1 soon and we don't want to release unfinished module. It also might be the best idea to cooperate with HttpComponents team to make our current HTTP codec (i.e. mina-filter-codec-http) and mina-core plug into HttpComponents NIO extension very easily. I'd like to know what the HttpComponents team think about this issue. Trustin -- what we call human nature is actually human habit -- http://gleamynode.net/ -- PGP Key ID: 0x0255ECA6
