GUI Protocol

We should probably decide what changes need to be made to the GUI protocol. I
know Meredydd is wanting to switch to a better authentication system than the
current cookie system, for example. I would also like to see some sort of
redundancy put in, seeing as currently the protocol doesn't really have any.
Theoretically any string of bytes is legally parsable, which makes it very
difficult for either end to resynchronize if it get's confused in any way.
I would like to have some type of begin and/or end marker that we can use to
find the next command in such cases. I suppose it really shouldn't be
necessary, but it would be good to have a way of at least detecting that we
are talking to a confused client. My logs are definitely showing cases where
somebody doesn't know where they are in the protocol...

-- 
Craig West         Ph: (416) 666-1645	|  It's not a bug,
[email protected]              	|  It's a feature...