[reSIProcate] ClientAuthManager & supporting different authentication schemes

[Alan Stokes]

Another thing I need to do is support a non-Digest authentication scheme on 
the client side.

It looks like I need to produce an alternative implementation of 
ClientAuthManager for that - but unfortunately it hasn't got any virtuals I 
can override. It looks to me like it needs a virtual destructor and that 
handle, addAuthentication and probably dialogSetDestroyed need to be 
virtual.

Is that right, or am I missing something? Would you normally declare a 
separate abstract base class for the interface and make ClientAuthManager 
implement it, or are you happy combining the interface with the base 
implementation? If this is the right thing to do, would you be interested in 
a patch?

- Alan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://list.resiprocate.org/pipermail/resiprocate-devel/attachments/20050913/4d579df1/attachment.htm>