From 33ca3e581544d7c040946340f1c3745f5bb8fa49 Mon Sep 17 00:00:00 2001 From: Petr Stefan Date: Thu, 23 Jun 2016 14:43:36 +0200 Subject: [PATCH] Updated Communication (markdown) --- Communication.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/Communication.md b/Communication.md index 71ecb7c..6bba7b3 100644 --- a/Communication.md +++ b/Communication.md @@ -27,8 +27,7 @@ requests to the _execution thread_, which handles them properly. Commands from _listening thread_ to _execution thread_: - **eval** - evaluate a job. Requires 3 message frames: - - `job_id` - identifier of this job (in ASCII representation -- we avoid endianness issues and also - support alphabetic ids) + - `job_id` - identifier of this job (in ASCII representation -- we avoid endianness issues and also support alphabetic ids) - `job_url` - URI location of archive with job configuration and submitted source code - `result_url` - remote URI where results will be pushed to @@ -153,8 +152,7 @@ server, its IP address and port is configurable in frontend. Commands from frontend to broker: - **eval** - evaluate a job. Requires at least 4 frames: - - `job_id` - identifier of this job (in ASCII representation -- we avoid endianness issues and also - support alphabetic ids) + - `job_id` - identifier of this job (in ASCII representation -- we avoid endianness issues and also support alphabetic ids) - `header` - additional header describing worker capabilities. Format must be `header_name=value`, every header shall be in a separate message frame. There is no maximum limit on number of headers. There may be also no headers at all. - empty frame (with empty string) - `job_url` - URI location of archive with job configuration and submitted source code