Commit 13768ea9 authored by Per Cederqvist's avatar Per Cederqvist
Browse files

(Articles, LysKOM Data Types): Don't say that the misc-info list will

	be removed in the future.  Move such speculation to a new appendix.
(Future changes): New appendix.
parent e6d639d5
......@@ -2,7 +2,6 @@
@c FIXME: Explain how the garb works with nice and keep-commented
@c FIXME: Make all types clickable in HTML (and info?)
@c FIXME: Move history to appendices
@c FIXME: Move predefined aux-items to separate chapter
@c FIXME: Move misc-infos to chapter?
@c FIXME: Check for too much text before @menu.
......@@ -11,7 +10,7 @@
@c FIXME: Name Expansion collate table info is outdated.
@c FIXME: sentence-end-double-space!
@c $Id: Protocol-A.texi,v 1.131 2001/05/01 16:41:03 ceder Exp $
@c $Id: Protocol-A.texi,v 1.132 2001/05/01 17:11:24 ceder Exp $
@c %**start of header
@settitle LysKOM Protocol A
......@@ -370,6 +369,7 @@ The most up-to-date version if this document can always be found at
* The User Area::
* Writing Clients::
* Importing and Exporting E-Mail::
* Future changes::
* Protocol Version History::
* Document Edition History::
* Index::
......@@ -467,9 +467,7 @@ user.
Currently there is an array of @type{Misc-Info} included in the
@type{Text-Stat}. This array contains information about recipients,
senders, comments and footnotes. In the future the information
contained in the @type{Misc-Info} array will be integrated into the
senders, comments and footnotes.
Every article has at least one number, the global article number. Global
numbers are assigned in ascending order to new articles, and are never
......@@ -2603,8 +2601,7 @@ values.
These two structures contain information about a single article.
@type{Text-Stat} contains core information about the article and
@type{Misc-Info} contains miscellaneous information related to the
article. In the future, @type{Misc-Info} will become obsolete and
@type{Text-Stat} will be extended with more information.
A @type{Text-Stat} consists of the following:
......@@ -8977,6 +8974,43 @@ When creating aux-items like @aux{mx-author}, text coded using the
method in RFC 2047 should be decoded.
@node Future changes
@appendix Future changes (speculative)
While useful and stable, this protocol is far from perfect. Here is a
short list of things the current developers would like to change in
future versions of the protocol. The list is not sorted.
All changes will be made in a backwards compatible way. Clients
will still be able to use the old requests.
@itemize @bullet
Cryptography! LysKOM is sometimes used for sensitive information. It
is unacceptable that everything is sent in the clear. Should we use
TLS? This area needs further study.
The information contained in the @type{Misc-Info} array should be
integrated into the @type{Text-Stat}. There should be one array of
recipients, one of texts that comments this text, and so on. This
would make the @type{Misc-Info} type obsolete.
The aux-items can be very large. It was a mistake to include them in
the @type{Text-Stat}. They should probably be separated from the
@type{Text-Stat}; retrieving the @type{Text-Stat} should only indicate
which aux-items that exists.
There is too few asynchronous messages. There are many situations
where something can change without a client noticing it.
There is more than one way to fix this, and it is not known which way
is the best.
@end itemize
@node Protocol Version History
@appendix Protocol Version History (informative)
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment