From wade@MIT.EDU Thu Feb 11 10:50:13 1993
Date: Thu, 11 Feb 93 10:43:21 EST
From: wade@MIT.EDU (Steven Wade Neiterman)
To: brlewis@MIT.EDU
Subject: [murphy@dccs.upenn.edu: TechInfo Protocol Document]


------- Forwarded Message

Return-Path: <murphy@dccs.upenn.edu>
Posted-Date: Wed, 23 Dec 92 13:27:31 -0500
To: techinfo@MIT.EDU
Subject: TechInfo Protocol Document
Date: Wed, 23 Dec 92 13:27:31 -0500
From: murphy@dccs.upenn.edu
X-Mts: smtp


I don't know if you've updated it, but you may find the following
useful:

------- Forwarded Message

Return-Path: murphy@dccs.upenn.edu
Received-Date: Wed, 18 Nov 92 13:00:36 -0500
Received: from STAFF.DCCS.UPENN.EDU by noc2.dccs.upenn.edu
        id AA05518; Wed, 18 Nov 92 13:00:34 -0500
Received: from noc2.dccs.upenn.edu by staff.dccs.upenn.edu
        id AA05795; Wed, 18 Nov 92 13:00:32 -0500
Received: from LAM.DCCS.UPENN.EDU by noc2.dccs.upenn.edu
        id AA05507; Wed, 18 Nov 92 13:00:31 -0500
Return-Path: <murphy@dccs.upenn.edu>
Received: by lam.dccs.upenn.edu
        id AA05340; Wed, 18 Nov 92 13:00:27 -0500
Date: Wed, 18 Nov 92 13:00:27 -0500
From: murphy@dccs.upenn.edu
Posted-Date: Wed, 18 Nov 92 13:00:27 -0500
Message-Id: <9211181800.AA05340@lam.dccs.upenn.edu>
To: david@penndrls.upenn.edu
Subject: new transactions
Cc: murphy@dccs.upenn.edu


Here are the new transactions that you might take advantage of
in the next release of your client.  They are not installed
on penninfo-srv  yet, but you can test against lam.dccs.upenn.edu or
marathon.mit.edu.

A: Change Source Information
Example:
A:DCCS:Data Communications:Linda Murphy:898-9534:murphy@dccs

BUG: I have to report a bug to MIT -- if I change
the source info for DCCS_ENG, it also changes the source info
for DCCS.  It seems to do a prefix match instead of an exact
match on the source name.

The client must authenticate as a provider to use the A: transaction.

H: Help
  Get the help menu from the server.

I: What's New
Example:
I:0:11:1:92

This sends non-menu items whose date is Nov 1st or after, starting
>from nodeid 0 (you can limit the range of the search by specifying a
different nodeid).

J: Full text search
It doesn't work yet on the test server.  The format is rumored to be:
J:searchstring:nodeid:maxdocs

K: Search on Source name
Example:
K:0:Library_Services

This will start at nodeid 0 and find all non-menu items belonging to 
source
Library_Services. Source name must be an exact match, not partial.

O: Flags format
O:1 
  server always sends 0 as the flags field
O:2
  Sends flags "unchanged" (not sure -- changed from what?)
  This seems to be the setting to use (the other new clients do)
O:3
  Not sure what this does.

- --lam

------- End of Forwarded Message


------- End of Forwarded Message