At 06:59 17/02/03, Alex Rousskov wrote:
0) Whether there are clear/strict client-server roles or
whether it is possible for the server to send requests
to the client.
1) Whether the protocol is based on (request, response)
transactions or on possibly isolated messages (i.e., a
"request" may not demand/expect a response)
2) Whether a single request/message can solicit or
trigger multiple responses (e.g., OPES server expanding
an SMTP recipient alias into several addresses and
handling those addresses differently for the same OPES
request)
3) How exceptions are delivered to the other party (e.g.,
"I am not interested in seeing any more of this message")
4) How the "preview" feature is handled. What
the data-granularity of an OPES data transaction is (whole
message, header+tail, arbitrary range, arbitrary collection
of bytes?)
Did I miss any? It would be nice to have a more-or-less complete list
so that one can find/propose a simple protocol covering all decision
points. We can then compare proposed solutions and fill in the
May I suggest that the OPES web master maintains a list on the site where
we could list these ideas. Then we could discuss their aggregation into a
minimum non conflicting list much more easily?
At this stage it could only be to paste them on an Excel page and to give
them a number. The target would be first to see the one we really need, the
ones wich means the same thing, etc.
jfc
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.454 / Virus Database: 253 - Release Date: 10/02/03