On Thu, Sep 06, 2001 at 11:20:07PM +0200, Benjamin Bruheim wrote:
In its current state there is no protocol specific issues. All it does is to return strings which the protocols may use. The reason I don't feel it shouldn't be in protocols is that it does not depend on anything in twisted for operation. Nor is it protocolbound, actually the logic place to use it is in passport.Identity. And generate the object otp.OTP each time the password is set. But if you wish, I can move it.
I'll leave it up to your judgement, just take what I said as a suggestion :-). The ultimate critera for where a particular thing should go would be where the majority of people would look for it in the codebase; and since I'm not someone who'd likely be looking for an OTP implementation, I don't know where I'd look for it. -- ______ __ __ _____ _ _ | ____ | \_/ |_____] |_____| |_____| |_____ | | | | @ t w i s t e d m a t r i x . c o m http://twistedmatrix.com/users/glyph