Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.toronto.edu!ietf-nntp-distribution-owner Date: Tue, 4 Jun 1991 19:55:50 -0400 Message-ID: <9106042355.AA16895@ftp.com> Original-To: Eliot Subject: Re: a new nntp draft From: seven@ftp.com (Benjamin M. Levy) Reply-To: seven@ftp.com Original-Cc: ietf-nntp@turbo.bio.net Sender: seven@ftp.com Repository: babyoil.ftp.com Originating-Client: hooks Newsgroups: list.ietf-nntp Distribution: list Sender: list-admin@cs.toronto.edu Approved: list.ietf-nntp@mail.cs.toronto.edu Lines: 33 From: Eliot To: ietf-nntp@turbo.bio.net Subject: a new nntp draft To that end, I now invite your comments about how a news reader protocol ought to be organized. For example: - Should the protocol retain an ASCII command interface, like NNTP? yes - How can we handle network database access? What interface should be provided for a database? Natural language? Some form of regular expression search? etc? IMAP-2 (RFC-1064) has a search command for mail messages. With it you can search for messages with a given string in CC, BODY, TO, and TEXT (entire msg). FROM and HEADER should be added to that list. Also you can search for messages sent BEFORE, SINCE, or ON a certain date. Also it would be useful to be able to exclude messages. Something I'd like to see added to NNRP, is a command for getting the size of a message (like STAT in POP3). Eliot Lear [lear@turbo.bio.net] -- ---Ben Levy FTP Software Inc. seven@ftp.com ----------------------------------------------------------------------- Member of the International Ameoba Society: "United We Stand, Divided We Multiply"