![]() This made saving attachments slower, and it caused undue disk fragmentation. Second, in anticipation of possibly having to retain the attachment data, Agent would simultaneously stream the attachment to both a file and to the folder. ![]() First, it could cause a folder to fill up if it contained a large number of messages with damaged attachments. Previously, when Agent detected an error in a binary attachment, its default action was to save the attachment but also keep a copy of the file in the message stored in Agent's folder. On modern servers retrieval by Message-ID has become more efficient and reliable, so we have made this the new default for body retrieval. Previously Agent's default was to retrieve by article number, and to revert to using the Message-ID only if that failed. Message bodies can be retrieved not only by article number but also by Message-ID. (The infamous is such a group.) We have updated Agent to store 64-bit article numbers, so that Agent is not likely to hit a limit anytime in the next millennium. ![]() ![]() With the growth in the amount of data available on Usenet and the long-term retention of this data by premium news services such as Fort?'s APN, some newsgroups have well over four gigabytes of headers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |