Some of us were talking about handling events, monitoring requests in progress, etc. the other day. This stuff could be useful for OCCI.<br><br>Sam<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>
From: <b class="gmail_sendername">Salvatore Loreto</b> <span dir="ltr">&lt;<a href="mailto:salvatore.loreto@ericsson.com">salvatore.loreto@ericsson.com</a>&gt;</span><br>Date: Thu, Jun 11, 2009 at 10:39 PM<br>Subject: Fwd: [hybi] draft-loreto-http-bidirectional<br>
To: <a href="mailto:apps-discuss@ietf.org">apps-discuss@ietf.org</a><br><br><br>-------- Original Message --------<br>
<br>
Hi there,<br>
<br>
we have just submitted the following draft:<br>
&quot;Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP&quot;<br>
<br>
The draft is a first tentative to describe what does it means to use HTTP for Bidirectional communication<br>
and how to better use HTTP, as it exists today, to enable such &quot;bidirectional HTTP&quot; using &quot;long polling&quot;<br>
and &quot;HTTP streaming&quot; mechanisms.<br>
<br>
until it will appear on the IETF website you can find it here:<br>
<a href="http://xmpp.org/internet-drafts/draft-loreto-http-bidirectional-00.txt" target="_blank">http://xmpp.org/internet-drafts/draft-loreto-http-bidirectional-00.txt</a><br>
<br>
we are looking forward to receive your comments, suggestions and feedbacks on it<br>
<br>
we would like to remind that the preferred venue for discussion of this document is the <a href="mailto:hybi@ietf.org" target="_blank">hybi@ietf.org</a> mailing list<br>
(visit &lt;<a href="https://www.ietf.org/mailman/listinfo/hybi" target="_blank">https://www.ietf.org/mailman/listinfo/hybi</a>&gt; for further information).<br>
<br>
best regards<br>
Sal<br>
<br>
<br>
-------- Original Message --------<br>
Subject:        New Version Notification for draft-loreto-http-bidirectional-00<br>
Date:   Thu, 11 Jun 2009 13:15:57 -0700 (PDT)<br>
From:   IETF I-D Submission Tool &lt;<a href="mailto:idsubmission@ietf.org" target="_blank">idsubmission@ietf.org</a>&gt;<br>
To:     <a href="mailto:Salvatore.Loreto@ericsson.com" target="_blank">Salvatore.Loreto@ericsson.com</a><br>
CC: <a href="mailto:salvatore.loreto@ericsson.com" target="_blank">salvatore.loreto@ericsson.com</a>,<a href="mailto:psaintan@cisco.com" target="_blank">psaintan@cisco.com</a>,<a href="mailto:gregw@webtide.com" target="_blank">gregw@webtide.com</a>,<a href="mailto:stefano.salsano@uniroma2.it" target="_blank">stefano.salsano@uniroma2.it</a> <br>

<br>
<br>
<br>
A new version of I-D, draft-loreto-http-bidirectional-00.txt has been successfuly submitted by Salvatore Loreto and posted to the IETF repository.<br>
<br>
Filename:        draft-loreto-http-bidirectional<br>
Revision:        00<br>
Title:           Best Practices for the Use of Long Polling and Streaming in Bidirectional HTTP<br>
Creation_date:   2009-06-11<br>
WG ID:           Independent Submission<br>
Number_of_pages: 16<br>
<br>
Abstract:<br>
There is widespread interest in using the Hypertext Transfer Protocol<br>
(HTTP) to enable asynchronous or server-initiated communication from<br>
a server to a client as well as from a client to a server.  This<br>
document describes how to better use HTTP, as it exists today, to<br>
enable such &quot;bidirectional HTTP&quot; using &quot;long polling&quot; and &quot;HTTP<br>
streaming&quot; mechanisms.<br>
                                                                                <br>
<br>
The IETF Secretariat.<br>
<br>
<br>
<br>
_______________________________________________<br>
hybi mailing list<br>
<a href="mailto:hybi@ietf.org" target="_blank">hybi@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/hybi" target="_blank">https://www.ietf.org/mailman/listinfo/hybi</a><br>
<br>
_______________________________________________<br>
Apps-Discuss mailing list<br>
<a href="mailto:Apps-Discuss@ietf.org" target="_blank">Apps-Discuss@ietf.org</a><br>
<a href="https://www.ietf.org/mailman/listinfo/apps-discuss" target="_blank">https://www.ietf.org/mailman/listinfo/apps-discuss</a><br>
</div><br>