I think that limiting the number of separate packages is good idea.
As Oleg has mentioned adding more packages really just adds overhead.
The only caveat I would add is that I think it's important to keep the
long term goals in mind, so that the code for cookies, auth, etc
remains independent even if packaged together.
It all depends how much time Mike can invest into developing and
maintaining HttpConn. If not much, we should seriously consider using
Commons Pool.
This is an open question. I still would like to contribute in this
area, but have had little time lately. Even if I am unable to get to
this I would still strongly recommend writing connection management in
house instead of using Commons Pool. From what I've seen it doesn't
fit the model we need for connection management. It also seems a
shame to add a dependency just for this.
Mike
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
