Changes between Version 6 and Version 7 of Master Slave Protocol

Timestamp:

Jun 23, 2005, 11:09:56 PM (19 years ago)

Author:

cmlenz

Comment:

Update build initiation messages

Master Slave Protocol

@@ -55 +55 @@
 If the client accepts a build request by sending a positive reply, the server will transmit a tarball of the code base that is to be built. The client does not need to know which exact revision (or branch) of the project it is building, nor does it need to perform a checkout itself.
 
+A client accepts a build request by responding with a {{{<download>}}}. for example:
+
+{{{
+  RPY 1 1 . 0 60
+  Content-Type: application/beep+xml
+
+  <download>
+   <accept type="application/tar" encoding="bzip2"/>
+   <accept type="application/tar" encoding="gzip"/>
+  </download>
+}}}
+
+In this message, the client indicates that it will accept {{{tar}}} archives with {{{bzip2}}} or {{{gzip}}} compression (preferring the former).
+
+After having received such a reply, the master can proceed by transmitting a snapshot of the code base to the slave:
+
 {{{
   MSG 1 2 * 0 78
   Content-Type: application/tar
-  Content-Encoding: gzip
+  Content-Disposition: myproject-r456.tar
+  Content-Transfer-Encoding: gzip
   
   ...