Or, just to get to know - you can take tcpdump and take a look :) I personally wouldn't call that HTTP. Something "HTTP-like" would describe it better. Because it's not request-response. It's just message passing, no need to wait for the answer - send new message one after another. Every message is POST with address and message type encoded in URI: POST /executor(1)/mesos.internal.RunTaskMessage. Sender is encoded in User-Agent header, e.g: libprocess/slave(1)@127.0.0.1:5051. Body contains protobuf message, Transfer-Encoding is always "chunked".
On Mon, Apr 7, 2014 at 10:42 PM, Benjamin Mahler <[email protected]>wrote: > Unfortunately you will need to learn this by looking at the code in > libprocess, as the message passing format is not explicitly documented at > the current time. > > Start with calls like ProtobufProcess::send() and dig your way down. > > > On Sat, Apr 5, 2014 at 7:52 AM, Vladimir Vivien > <[email protected]>wrote: > > > I was watching this video from > > https://www.youtube.com/watch?v=n5GT7OFSh58from Ben where he talked > > about the wire protocol for Mesos being done in > > HTTP. > > > > Where can I learn about the low-level wire protocol either in > documentation > > or browsing through the code. > > > > Thanks. > > > > -- > > Vladimir Vivien > > >
