Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.toronto.edu!ietf-nntp-distribution-owner Date: Wed, 5 Jun 1991 11:35:30 -0400 Message-ID: <9106051535.AA07413@delfiini.funet.fi> From: ojala@funet.fi (Petri Ojala) Sender: ojala@delfiini.funet.fi Original-To: Eliot Original-Cc: ietf-nntp@turbo.bio.net References: Subject: a new nntp draft X-Charset: ASCII X-Char-Esc: 29 Newsgroups: list.ietf-nntp Distribution: list Sender: list-admin@cs.toronto.edu Approved: list.ietf-nntp@mail.cs.toronto.edu Lines: 29 > - Should the protocol retain an ASCII command interface, like NNTP? Absolutely. It makes the debugging and client writing much easier. A complex protocol usually requires a complex language to use it but system like News should be possible to be used by a Perl script for example. > - How can we handle network database access? What interface should be > provided for a database? Natural language? Some form of regular > expression search? etc? I think that regexp would be reasonably enough if the search can be limited to certain basic news components like receiver, subject, header or body text. One idea might be to be able to define a number of search rules (what to search, what to exclude, where to search) and then do the actual search based on the previously defined rules. This would make the search very flexible. > Comments? 8bit transparency ? I think that it would be a good idea to have the 8bit support mentioned for the protocol already. The NETF-MHS proposal for 8bit support will include 'magic cookie' for 8bit detection in the HELO-message (SMTP). This might be a possible addition to the new NNTP protocol too ? Regards, Petri Ojala