Author StevenJ
Recipients StevenJ, ajvant, chasonr, christian.heimes, giampaolo.rodola, janssen, jelie, pitrou
Date 2010-11-06.17:22:59
SpamBayes Score 9.07957e-07
Marked as misclassified No
Message-id <1289064186.46.0.691566209426.issue1926@psf.upfronthosting.co.za>
In-reply-to
Content
The only comment I have is, if the caller needs to organise when to auth and instigate tls then for completeness getcapabilities() should have an option to force a reget of the current capabilities, in line with rfc3977 5.2.2:

> An NNTP client MAY cache the results of this command, but MUST NOT 
> rely on the correctness of any cached results, whether from earlier
> in this session or from a previous session, MUST cope gracefully 
> with the cached status being out of date, and SHOULD (if caching
> results) provide a way to force the cached information to be
> refreshed.

As it stands, the nntplib can cause the cached capabilities to be refreshed at certain points automatically (as it should), but I 
think it should be possible for the caller of the method to also specify that fresh capabilities are required and not cached ones.

something like this perhaps? :

mynntp.getcapabilites(refresh=True)
History
Date User Action Args
2010-11-06 17:23:06StevenJsetrecipients: + StevenJ, janssen, pitrou, giampaolo.rodola, christian.heimes, chasonr, ajvant, jelie
2010-11-06 17:23:06StevenJsetmessageid: <1289064186.46.0.691566209426.issue1926@psf.upfronthosting.co.za>
2010-11-06 17:23:00StevenJlinkissue1926 messages
2010-11-06 17:22:59StevenJcreate