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 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
