On 8/1/06, peter royal <[EMAIL PROTECTED]> wrote:

On Jul 31, 2006, at 2:21 PM, Irving, Dave wrote:
> On the other hand, I believe that there is a huge amount which
> asyncweb
> can learn from the existing http commons work - for example, I suspect
> http commons provides a far more "robust" implementation of the spec -
> something Im very keen to work towards.

One area in which AsyncWeb can probably leverage http commons stuff
would be in cookie and other header parsing. I'm sure there are
others as well.


Additionally, AsyncWeb is about server and http commons is about client for
now.  I think we can do both side in parallel and see what can be shared
between them as time goes by, but not right now.  It's good to have both
client and server side, right?

Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP key fingerprints:
* E167 E6AF E73A CBCE EE41  4A29 544D DE48 FE95 4E7E
* B693 628E 6047 4F8F CFA4  455E 1C62 A7DC 0255 ECA6

Reply via email to