Node:Future changes, Next:Protocol Version History, Previous:Some Client-specific Aux-Item Types, Up:Top
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.
Misc-Infoarray should be integrated into the
Text-Stat. There should be one array of recipients, one of texts that comments this text, and so on. This would make the
Misc-Infotype obsolete. (This is bug 134.)
Text-Stat. They should probably be separated from the
Text-Stat; retrieving the
Text-Statshould only indicate which aux-items that exists. (This is bug 135.)
There is more than one way to fix this, and it is not known which way is the best. (This is bug 93.)
One way to fix this is to remove the
original bit and
followups-to field in the
Doing this in a backwards-compatible way requires some thought...
read-textsfields of a
Membershipis a very poor way to store information about what is read. Consider the case where somebody has read everything up to text 100, and text 102-2002. Using the current protocol specification more than 2000 numbers must be transmitted to convey that information. A much more attractive solution would be to send a list of ranges of read texts. (This is bug 52.)
mark-as-readcall is a reasonably good way to mark a single text as read (but one could argue that it should take a single
ARRAY Conf-Noas arguments), but there is no easy way to undo such an operation. You can use
set-last-readfollowed by a number of
mark-as-readcalls to get the desired effect, but it would be nice to have a
mark-as-unreadcall. (This is bug 53.)
In the future, a new call might be added, so that a client can give
the server explicit permission to reorder the replies. The client
would then have to rely on the
ref-no to match each reply to
the corresponding call. (This is
For more information about potential future changes, see Bugzilla @ Lysator.