hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrea Selva" <selva.an...@gmail.com>
Subject Re: Final classes and methods
Date Fri, 16 May 2008 07:08:49 GMT
I think that a better way should be to subclass the parent of the final
classes, (tipically an abstract class) and delegate the necessary calls to
the Basic, and mantain the modified logic in the subclass...but every case
is different from another, i've nto the details.
Best regards

On Fri, May 16, 2008 at 4:03 AM, Sam Berlin <sberlin@gmail.com> wrote:

> > Hmm... As I'm typing this, I an idea came to me. Originally, I had
> dismissed using a separate client class because it would be difficult to tie
> the connection limits together. What just occurred to me (duh), is that the
> connection manager is a separate object. The second client class wouldn't
> use any request interceptors. Can you see any problems with sharing the same
> instance of connection manager between two different client objects/classes?
> AFAIK, that's a perfectly valid use.  (Whether or not it's the
> intended use... I'm not sure.  We definitely use it that way within
> LimeWire, though.)
> Sam
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
> For additional commands, e-mail: dev-help@hc.apache.org

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message