Changes between Version 8 and Version 9 of Master Slave Protocol Http

Timestamp:

Jul 24, 2007, 4:03:42 PM (17 years ago)

Author:

cmlenz

Comment:

Use of cookies

Master Slave Protocol Http

@@ -43 +43 @@
 HTTP/1.1 201 Created
 Location: http://example.org/builds/trunk/123/
+Set-Cookie: slave=lamech; Path=/builds/trunk/123/
 }}}
 
 The response contains the URL to a build recipe as the value of the `Location` header. At this point, the master has allocated a pending build entity in its database. The progress on this build can be viewed as HTML at the specified URL using any HTTP user agent.
+
+The master also sets a cookie on the slave so that it can be identified on subsequent requests. In the example above, the cookie contains only the slave name; we'll probably need to include more information, such as when the build was started.
 
 On the other hand, if the master has no work for the slave, it would return a `204 No Content` response:
@@ -53 +56 @@
 HTTP/1.1 204 No Content
 }}}
+
+  ''Open issue: we'd need to either repost the slave name/info with every request, or set a cookie that identifies the slave on subsequent requests.''
 
 == Build Initiation ==
@@ -62 +67 @@
 GET /builds/trunk/123/ HTTP/1.1
 Host: example.org
+Cookie: slave=lamech
 Accept: application/x-bitten+xml
 }}}
@@ -112 +118 @@
 PUT /builds/trunk/123/steps/test/ HTTP/1.1
 Host: example.org
+Cookie: slave=lamech
+Content-Type: application/x-bitten+xml
+Content-Length: 666
 
 <result status="success" started="2005-06-29T16:41:53" duration="7.61">
@@ -137 +146 @@
 PUT /builds/trunk/123/files/foobar-r123.tar.gz HTTP/1.1
 Host: example.org
+Cookie: slave=lamech
 Content-Type: application/tar
 Content-Encoding: gzip