[jira] [Commented] (MESOS-3566) Add a section to the Scheduler HTTP API docs around RecordIO specification

["Ben Whitehead (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MESOS-3566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14947282#comment-14947282 ] 

Ben Whitehead commented on MESOS-3566:
--------------------------------------

I would prefer there to be some documentation on RecordIO independent of the http api itself, this will make it much easier to locate the spec later and make it referenceable by other things.

Having something as explicitly spec'd as http chunked transfer encoding would be preferable: Similar to how http chunked transfer encoding is spec'd out: http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.6.1

> Add a section to the Scheduler HTTP API docs around RecordIO specification
> --------------------------------------------------------------------------
>
>                 Key: MESOS-3566
>                 URL: https://issues.apache.org/jira/browse/MESOS-3566
>             Project: Mesos
>          Issue Type: Improvement
>            Reporter: Anand Mazumdar
>              Labels: mesosphere
>
> Since the {{RecordIO}} format is not that widely used, searching for it online does not offer much help. 
> - It would be good if we can add to the docs, a small section on its specification for framework developers. 
> - Bonus points, if we can have a simple code snippet in C++/Java on reading a {{RecordIO}} response to help developers.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)