Can you explain a concrete problem you are trying to solve? Without a concrete problem, I am not sure where this would be specifically useful over other options.
What this looks like at face-value is a long poll ( http://en.wikipedia.org/wiki/Push_technology). The standard http communication you originally referred to as "push" pattern is actually a request-response pattern. The client issues an http request, and the server responds. What you have proposed now is more of a push pattern, because the client "subscribes" to a channel by hitting an endpoint and waiting with interest. When something of interest becomes available, the server will then push to a client. Now that being said, it is one option for an http client to subscribe to specific information and wait for it to be ready. But it isn't necessarily more flexible or robust than a websocket approach, which is actually true bi-directional. The server/client connection would be established, and either side is free to send or receive, according to some established protocol. In your example, the client is subscribing to a specific request, since it must hit an endpoint of a determined type to express interest in something. It cannot change its request at this point, and it expects to receive "something". You could easily decide to send structure you want though, and have the client take different actions, to make it a generic communication push system. Basically, socket-io does all of these techniques combined, in order to provide a highly-compatible solution of fallback mechanisms. Then there is also the new Server Sent Events spec: http://www.w3.org/TR/eventsource/ Basically, these techniques exist. Are you trying to do something a bit different than these approaches to solve a different problem? Justin On Mon, Mar 9, 2015 at 10:13 PM Marcus Ottosson <[email protected]> wrote: > I’d like to you by you to hear what you think of it. > > That’s some literacy excellence, right there. :) > > > -- > You received this message because you are subscribed to the Google Groups > "Python Programming for Autodesk Maya" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOCCmk5mrOcz0dXtGCvGaN7RqMZZgiTXmg3TPnzTZDu_0A%40mail.gmail.com > <https://groups.google.com/d/msgid/python_inside_maya/CAFRtmOCCmk5mrOcz0dXtGCvGaN7RqMZZgiTXmg3TPnzTZDu_0A%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Python Programming for Autodesk Maya" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/python_inside_maya/CAPGFgA26yRiTejtC6avJN6x2LzAUZzbL9E_1xZZpLy91QYOjAQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
