docs/custom-transfers: Add empty lines for good Markdown style

Signed-off-by: Steffen Prohaska <prohaska@zib.de>
This commit is contained in:
Steffen Prohaska 2017-04-23 10:21:03 +02:00
parent faee8e6381
commit aef5375990
No known key found for this signature in database
GPG Key ID: CD4EF2ED1339052C

@ -79,6 +79,7 @@ request / response metadata. The metadata exchanged is always in JSON format.
External files will be referenced when actual content is exchanged. External files will be referenced when actual content is exchanged.
### Line Delimited JSON ### Line Delimited JSON
Because multiple JSON messages will be exchanged on the same stream it's useful Because multiple JSON messages will be exchanged on the same stream it's useful
to delimit them explicitly rather than have the parser find the closing `}` in to delimit them explicitly rather than have the parser find the closing `}` in
an arbitrary stream, therefore each JSON structure will be sent and received on an arbitrary stream, therefore each JSON structure will be sent and received on
@ -101,6 +102,7 @@ data to the process over stdin. This tells the process useful information about
the configuration. the configuration.
The message will look like this: The message will look like this:
```json ```json
{ "event":"init", "operation":"download", "concurrent": true, "concurrenttransfers": 3 } { "event":"init", "operation":"download", "concurrent": true, "concurrenttransfers": 3 }
``` ```