git/sideband.h

#ifndef SIDEBAND_H
#define SIDEBAND_H

#define SIDEBAND_PROTOCOL_ERROR -2
#define SIDEBAND_REMOTE_ERROR -1

#define DEFAULT_PACKET_MAX 1000
#define LARGE_PACKET_MAX 65520

int recv_sideband(const char *me, int in_stream, int out, int err);
ssize_t send_sideband(int fd, int band, const char *data, ssize_t sz, int packet_max);

#endif
Move sideband client side support into reusable form. This moves the receiver side of the sideband support from fetch-clone.c to sideband.c and its header file, so that archiver protocol can use it. Signed-off-by: Junio C Hamano <junkio@cox.net> 2006-09-10 10:06:33 +02:00			`#ifndef SIDEBAND_H`
			`#define SIDEBAND_H`

			`#define SIDEBAND_PROTOCOL_ERROR -2`
			`#define SIDEBAND_REMOTE_ERROR -1`

			`#define DEFAULT_PACKET_MAX 1000`
Prepare larger packet buffer for upload-pack protocol. The original side-band support added to the upload-pack protocol used the default 1000-byte packet length. The pkt-line format allows up to 64k, so prepare the receiver for the maximum size, and have the uploader and downloader negotiate if larger packet length is allowed. Signed-off-by: Junio C Hamano <junkio@cox.net> 2006-09-11 01:27:08 +02:00			`#define LARGE_PACKET_MAX 65520`
Move sideband client side support into reusable form. This moves the receiver side of the sideband support from fetch-clone.c to sideband.c and its header file, so that archiver protocol can use it. Signed-off-by: Junio C Hamano <junkio@cox.net> 2006-09-10 10:06:33 +02:00
atomic write for sideband remote messages It has been a few times that I ended up with such a confusing display: \|remote: Generating pack... \|remote: Done counting 17 objects. \|remote: Result has 9 objects. \|remote: Deltifying 9 objects. \|remote: 100% (9/9) done \|remote: Unpacking 9 objects \|Total 9, written 9 (delta 8), reused 0 (delta 0) \| 100% (9/9) done The confusion can be avoided in most cases by writing the remote message in one go to prevent interleacing with local messages. The buffer declaration has been moved inside recv_sideband() to avoid extra string copies. Signed-off-by: Nicolas Pitre <nico@cam.org> Signed-off-by: Junio C Hamano <junkio@cox.net> 2006-10-11 17:49:15 +02:00			`int recv_sideband(const char *me, int in_stream, int out, int err);`
Move sideband server side support into reusable form. The server side support; this is just the very low level, and the caller needs to know which band it wants to send things out. Signed-off-by: Junio C Hamano <junkio@cox.net> (cherry picked from b786552b67878c7780c50def4c069d46dc54efbe commit) 2006-09-10 12:20:24 +02:00			`ssize_t send_sideband(int fd, int band, const char *data, ssize_t sz, int packet_max);`
Move sideband client side support into reusable form. This moves the receiver side of the sideband support from fetch-clone.c to sideband.c and its header file, so that archiver protocol can use it. Signed-off-by: Junio C Hamano <junkio@cox.net> 2006-09-10 10:06:33 +02:00
			`#endif`