List this is OT but may be of just enough interest to those following
David's emails, that I am going to cc occi-wg.
Check out: http://www.reversehttp.net/reverse-http-spec.html
It's a way to make each node be a server and a client. Built by one of our lot.
I wasn't aware of Reverse HTTP. It looks quite interesting and I'm
surprised we haven't heard more of it yet.
Just as reminder for those who didn't follow, LLUP is a simple messaging
format which focuses on making each message as stateless as possible while
carrying contextual information that would allow any recipient to consume,
interpret and perform intelligent actions on each message.
This is obviously particularly suited to the cloud since each node within
doesn't really need to know nor even care how the message arrived. It just
sees a message, deals with it and pushes another message to the cloud.
Like David said: decentralized, heterogeneous cloud environment.
In that context, Reverse HTTP is rather interesting to transport LLUP
messages since LLUP doesn't care about this aspect. As far as it goes you
could use HTTP, XMPP or pigeons. The only important aspect from LLUP's
perspective is the fact the message is in the cloud and some node will
pick it up.
Sylvain - thanks! I'm cc'ing Tony who wrote the reverse http spec.
I suspect this is now OT for OCCI, but please continue directly, or if
enough OCCI-WG people are interested, on-list.