| commit | 2a5c8cb46c797b756b247d57f70a90d3939e149c | |
| author | Shawn O. Pearce <spearce@spearce.org> | |
| Wed, 7 Oct 2009 01:43:41 +0000 (6 18:43 -0700) | ||
| committer | Shawn O. Pearce <spearce@spearce.org> | |
| Tue, 12 Jan 2010 19:56:55 +0000 (12 11:56 -0800) | ||
| tree | 9cd3806b4f03919e42b955d47ea6b475fdd1fe98 | treesnapshot (tar.gz zip) |
| parent | 3f8fdc03253264cae2172c168b5c959ea09a4c9d | commitdiff |
Teach ReceivePack how to use an RPC style interface
If biDirectionalPipe is false ReceivePack does not start out with the
advertisement but instead assumes it should read the command set once,
process that, and write the status report out. This means it only is
doing one read through the input followed by one write to the output,
which fits with the HTTP request processing model, and any other type
of RPC system... assuming that the payload for input can be a very big
entity like the command stream followed by the pack file.
Change-Id: I6f31f6537a3b7498803a8a54e10b0622105718c1
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
If biDirectionalPipe is false ReceivePack does not start out with the
advertisement but instead assumes it should read the command set once,
process that, and write the status report out. This means it only is
doing one read through the input followed by one write to the output,
which fits with the HTTP request processing model, and any other type
of RPC system... assuming that the payload for input can be a very big
entity like the command stream followed by the pack file.
Change-Id: I6f31f6537a3b7498803a8a54e10b0622105718c1
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
| org.eclipse.jgit/src/org/eclipse/jgit/transport/ReceivePack.java | diffblobblamehistory |