sid%FRIDAY.uucp@uunet.uu.net (Sid Shapiro) (10/11/89)
Figure out where to get a later version, I will.
My unix nntp servers (1.5) don't understand the XUPDGROUP command.
What is this command trying to do and what version of NNTP do I need
to have it recognized? I thought 1.5 was tha latest?
Thanks again,
/ Sid /gih900@UUNET.UU.NET (Geoff Huston) (10/11/89)
>My unix nntp servers (1.5) don't understand the XUPDGROUP command. >What is this command trying to do and what version of NNTP do I need >to have it recognized? I thought 1.5 was tha latest? To quote from the NNTP RFC (977) "There is no prohibition against additional commands being added; however it is recommended that any such unspecified command begin with the letter "X" to avoid conflict with later revisions of this specification." The problem I faced with NNTP on VMS is that the server / client relationship is slightly "tighter" than the conventional unix-based implementations. Instead of clients being associated with reader agents, a client in VMS may be a news database, and must be regularly updated against the server. In updating the client database, the client must delete records relating to items no longer held on the server, and add new records matching new server items. To add new records requires not only the message-ids of the new items, but also their date, subject field, line count and so on. To make this more efficient between VMS systems I implemented the XUPDGROUP command to make this update as fast as possible. BUT the code looks for a command unrecognised response from the server, and if the server does not respond to the XUPDGROUP command, the client will use a set of NEWNEWS and HEADER commands to acheive the same functional result (but take more time). So yes, you should see something in the Unix logs objecting to the XUPDGROUP command, but the client should still be OK - if not then there's a bug somewhere!!!!! Geoff Huston