RFC: Command server protocol

Matt Mackall mpm at selenic.com
Tue Jun 21 15:29:31 CDT 2011


On Tue, 2011-06-21 at 16:09 +0300, Idan Kamara wrote:
> On Sun, Jun 12, 2011 at 7:15 PM, Idan Kamara <idankk86 at gmail.com> wrote:
> > Here's an overview of the current protocol used by the command server
> > [snip]
> > When starting the server, it will send a new-line separated list of
> > capabilities (on the 'o' channel), in this format:
> > capabilities:\n
> > capability1\n
> > capability2\n
> > ...
> > At the most basic level, the server will support the 'runcommand'
> > capability.
> > [snip]
> 
> I think we may want the server to send something on the 'r'esult channel,
> (like 'ready' or something), once it finished sending the hello message.

This sounds like the thing I was getting at a while ago. But at this
point, I think we should simply require that the initial hello all fit
in one 'o' segment.

We can put guidelines in the protocol doc that they must ignore fields
in the hello message they don't understand.

-- 
Mathematics is the supreme nostalgia of our time.




More information about the Mercurial-devel mailing list