[PATCH 02 of 15] speedy: stub history query server

Idan Kamara idankk86 at gmail.com
Thu Dec 13 03:07:03 CST 2012


(you're top posting)

On Thu, Dec 13, 2012 at 12:09 AM, Tomasz Kłeczek
<tomasz.kleczek at gmail.com> wrote:
> Thanks. One problem that i see right away is that command server protocol
> doesn't allow you to send newlines in the data section.
> Communication between speedy client and server requires sending potentially
> big amount of binary data over the network and I would
> like to avoid overhead such as base64 encoding..

The data section has no restrictions on what it contains.

You could be confused with the hello message that has a specific
format (which uses new lines to separate fields).

>
>
> On Wed, Dec 12, 2012 at 1:57 PM, Idan Kamara <idankk86 at gmail.com> wrote:
>>
>> On Tue, Dec 11, 2012 at 8:38 PM, Tomasz Kleczek <tkleczek at fb.com> wrote:
>> > # HG changeset patch
>> > # User Tomasz Kleczek <tkleczek at fb.com>
>> > # Date 1355245443 28800
>> > # Branch stable
>> > # Node ID 5d51bf818878db395e2e1f840769a83254c3dcfd
>> > # Parent  13c6bcb8dd900dc7dbf5e3da9ef68d56fed250b3
>> > speedy: stub history query server
>> >
>> > Introduce a server component to which clients delegate their
>> > history requests.
>>
>> Sounds like you could use the command server for this by
>> adding new commands to it and making it work with TCP sockets.
>>
>> Yuya already monkey patched it to work over Unix sockets so it's
>> worth peeking at his stuff, and in general his work on chg might
>> help you in some way.
>>
>> https://bitbucket.org/yuja/chg
>> _______________________________________________
>> Mercurial-devel mailing list
>> Mercurial-devel at selenic.com
>> http://selenic.com/mailman/listinfo/mercurial-devel
>
>


More information about the Mercurial-devel mailing list