Hi Tom,
If the initial subscription HTTP connection fails the scheduler will not be
'subscribed' ( or its old equivalent : 'registered' ) so it won't be
possible to continue making other POST requests. Please refer to the
disconnections part of the doc for more details on already 'subscribed'
Thanks for sharing this Vinod, very clear and useful document!
Q: Could you explain in a little detail why the decision was made to use a
single HTTP endpoint rather than something like /event (for the stream) and
/call for making calls? It seems a little strange / contrived to me that the
On Fri, May 1, 2015 at 2:23 AM, Tom Arnfeld t...@duedil.com wrote:
Q: Could you explain in a little detail why the decision was made to use a
single HTTP endpoint rather than something like */event* (for the stream)
and */call* for making calls? It seems a little strange / contrived to me
Revised and moved the doc over to:
https://docs.google.com/document/d/1pnIY_HckimKNvpqhKRhbc9eSItWNFT-priXh_urR-T0/edit?usp=sharing
Please take another look if you have seen the doc previously as there were
some non-trivial changes (e.g., 1 endpoint instead of 2 endpoints).
On Wed, Apr
Hello,
We made some final changes on the doc, so I'm updating this thread to point
out that all changes are reflected on a small prototype of the API that you
can find here https://github.com/jimenez/mesos-APIproto.
Please feel free to comment on the new changes on the design doc.
Thanks,
Isabel
I would like to take this opportunity to move the doc from Twitter domain so
that I dont have to manually grant access to each new viewer. I'll post the new
doc link tomorrow.
@vinodkone
On Apr 29, 2015, at 8:54 AM, Isabel Jimenez contact.isabeljime...@gmail.com
wrote:
Hello,
We
6 matches
Mail list logo
