<?xml version="1.0" encoding="UTF-8"?>











<rss version="2.0" xmlns:jf="http://www.jivesoftware.com/xmlns/jiveforums/rss">



<channel>
    <title>Support Forums: Message List - Web 2.0 Communication Layer: from HTTP to Comet to Internet Mess</title>
    <link>http://www.theserverside.com</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    
        <generator>Jive Forums Silver 5.5.30 (www.jivesoftware.com)</generator>
    
    <pubDate>Sun, 26 May 2013 02:36:16 -0400</pubDate>


    <item>

        <title>XmlHttpRequest BAD - messaging GOOD</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=42641</link>

        

        
            <description><![CDATA[I have <a href="http://blogs.webtide.com/gregw/2006/10/18/1161164940000.html">blogged</a> a reply in length:...]]></description>
        

        <pubDate>Wed, 18 Oct 2006 12:13:18 -0400</pubDate>

        

        <jf:creationDate>Wed, 18 Oct 2006 12:13:18 -0400</jf:creationDate>
        <jf:modificationDate>Wed, 18 Oct 2006 12:13:18 -0400</jf:modificationDate>
        <jf:date>Oct 18, 2006</jf:date>
        <jf:author>gregw</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Sounds like BEEP</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=42641</link>

        

        
            <description><![CDATA[Actually, XMPP might cut it (it doesn't all have to be xml does it?). I only say this b/c if the projects like smack gain enough traction than enough features may get developed to make it compelling. I read they are working on an AS3 port on the forum...]]></description>
        

        <pubDate>Wed, 18 Oct 2006 05:49:05 -0400</pubDate>

        

        <jf:creationDate>Wed, 18 Oct 2006 05:49:05 -0400</jf:creationDate>
        <jf:modificationDate>Wed, 18 Oct 2006 05:49:05 -0400</jf:modificationDate>
        <jf:date>Oct 18, 2006</jf:date>
        <jf:author>Jin Chun</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Web 2.0 Communication Layer: from HTTP to Comet to Internet</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=42641</link>

        

        
            <description><![CDATA[Maybe ICE from ZeroC already fits.

Guido]]></description>
        

        <pubDate>Wed, 18 Oct 2006 02:34:50 -0400</pubDate>

        

        <jf:creationDate>Wed, 18 Oct 2006 02:34:50 -0400</jf:creationDate>
        <jf:modificationDate>Wed, 18 Oct 2006 02:34:50 -0400</jf:modificationDate>
        <jf:date>Oct 18, 2006</jf:date>
        <jf:author>Guido Anzuoni</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Sounds like BEEP</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=42641</link>

        

        
            <description><![CDATA[XMMP does not cut it. It is a fine protocol but not suitable for Coach Wei's internet service bus. The problems are that it is suitable for XML only and that it can only send one message at the same time. If you need to do more, you must set up a direct...]]></description>
        

        <pubDate>Tue, 17 Oct 2006 16:05:07 -0400</pubDate>

        

        <jf:creationDate>Tue, 17 Oct 2006 16:05:07 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 17 Oct 2006 16:05:07 -0400</jf:modificationDate>
        <jf:date>Oct 17, 2006</jf:date>
        <jf:author>Erik van Oosten</jf:author>
        <jf:replyCount>1</jf:replyCount>
    </item>


    <item>

        <title>Re: Web 2.0 Communication Layer: from HTTP to Comet to Internet</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=42641</link>

        

        
            <description><![CDATA[<blockquote><blockquote>Why not call it transmission control protocol or even internet protocal.  Heck, call it TCP/IP for short.</blockquote>Well, the obvious answer to my mind is that TCP/IP doesn't guarantee delivery or order. So that would eliminate...]]></description>
        

        <pubDate>Tue, 17 Oct 2006 11:48:38 -0400</pubDate>

        

        <jf:creationDate>Tue, 17 Oct 2006 11:48:38 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 17 Oct 2006 11:48:38 -0400</jf:modificationDate>
        <jf:date>Oct 17, 2006</jf:date>
        <jf:author>Guido Anzuoni</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Web 2.0 Communication Layer: from HTTP to Comet to Internet</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=42641</link>

        

        
            <description><![CDATA[<blockquote><blockquote>Why not call it transmission control protocol or even internet protocal.  Heck, call it TCP/IP for short.</blockquote>Well, the obvious answer to my mind is that TCP/IP doesn't guarantee delivery or order. So that would eliminate...]]></description>
        

        <pubDate>Tue, 17 Oct 2006 07:46:24 -0400</pubDate>

        

        <jf:creationDate>Tue, 17 Oct 2006 07:46:24 -0400</jf:creationDate>
        <jf:modificationDate>Tue, 17 Oct 2006 07:46:24 -0400</jf:modificationDate>
        <jf:date>Oct 17, 2006</jf:date>
        <jf:author>Jacques Ledoux</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>TCP does guarantee...</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=42641</link>

        

        
            <description><![CDATA[Mr. Ottinger, TCP most certainly does guarantee in-order, once-and-only-once, and error-free transmission of packets (or an error in the process).  Of course, as for the point of this article, TCP doesn't provide a server-push model.  And IP doesn't have...]]></description>
        

        <pubDate>Mon, 16 Oct 2006 23:29:23 -0400</pubDate>

        

        <jf:creationDate>Mon, 16 Oct 2006 23:29:23 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 16 Oct 2006 23:29:23 -0400</jf:modificationDate>
        <jf:date>Oct 16, 2006</jf:date>
        <jf:author>Dan Kirkpatrick</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Web 2.0 Communication Layer: from HTTP to Comet to Internet</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=42641</link>

        

        
            <description><![CDATA[I really like P2P technologies. Some time ago, I and a partner modeled a workflow system based in a P2P interface. Just like we receive messages with MSN Messenger, we planned to receive work lists, work items and other notifications via P2P and IM....]]></description>
        

        <pubDate>Mon, 16 Oct 2006 17:28:29 -0400</pubDate>

        

        <jf:creationDate>Mon, 16 Oct 2006 17:28:29 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 16 Oct 2006 17:28:29 -0400</jf:modificationDate>
        <jf:date>Oct 16, 2006</jf:date>
        <jf:author>Flavio Lima</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>It's here now! It's called ActiveMQ/Jetty</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=42641</link>

        

        
            <description><![CDATA[Wow, it's nice that folks are catching on to this.  Apache ActiveMQ and Jetty have been working in tandem to provide a highly scalable message bus API to javascript clients and it's been available for several months!...]]></description>
        

        <pubDate>Mon, 16 Oct 2006 17:20:29 -0400</pubDate>

        

        <jf:creationDate>Mon, 16 Oct 2006 17:20:29 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 16 Oct 2006 17:20:29 -0400</jf:modificationDate>
        <jf:date>Oct 16, 2006</jf:date>
        <jf:author>Hiram Chirino</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Web 2.0 Communication Layer: from HTTP to Comet to Internet</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=42641</link>

        

        
            <description><![CDATA[Robert,...]]></description>
        

        <pubDate>Mon, 16 Oct 2006 16:41:18 -0400</pubDate>

        

        <jf:creationDate>Mon, 16 Oct 2006 16:41:18 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 16 Oct 2006 16:41:18 -0400</jf:modificationDate>
        <jf:date>Oct 16, 2006</jf:date>
        <jf:author>mattjive</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>SIP will fix this issue</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=42641</link>

        

        
            <description><![CDATA[Session Intiation Protocol can do the push and pull and is the http protocol for devises and we can seamlessly move from a IP phone to a brower to an IVR etc]]></description>
        

        <pubDate>Mon, 16 Oct 2006 16:35:07 -0400</pubDate>

        

        <jf:creationDate>Mon, 16 Oct 2006 16:35:07 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 16 Oct 2006 16:35:07 -0400</jf:modificationDate>
        <jf:date>Oct 16, 2006</jf:date>
        <jf:author>jayant thomas</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Web 2.0 Communication Layer: from HTTP to Comet to Internet</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=42641</link>

        

        
            <description><![CDATA[How scalable are open connections via XMPP.  On a typical dual processor machine with 2GB of RAM, how may open connections can be handled?

With federation can I actually connect two people/clients between two servers?]]></description>
        

        <pubDate>Mon, 16 Oct 2006 15:52:08 -0400</pubDate>

        

        <jf:creationDate>Mon, 16 Oct 2006 15:52:08 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 16 Oct 2006 15:52:08 -0400</jf:modificationDate>
        <jf:date>Oct 16, 2006</jf:date>
        <jf:author>robert piotrowski</jf:author>
        <jf:replyCount>2</jf:replyCount>
    </item>


    <item>

        <title>Re: Web 2.0 Communication Layer: from HTTP to Comet to Internet</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=42641</link>

        

        
            <description><![CDATA[<blockquote>For short, I think we (maybe) need a stateful protocol, another generation of client platform with some basic server abilities and fixed IP addresses.<br><br>Is this it?</blockquote>...]]></description>
        

        <pubDate>Mon, 16 Oct 2006 13:43:36 -0400</pubDate>

        

        <jf:creationDate>Mon, 16 Oct 2006 13:43:36 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 16 Oct 2006 13:43:36 -0400</jf:modificationDate>
        <jf:date>Oct 16, 2006</jf:date>
        <jf:author>mattjive</jf:author>
        <jf:replyCount>4</jf:replyCount>
    </item>


    <item>

        <title>HTTP-NG tried to address these issues</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=42641</link>

        

        
            <description><![CDATA[The W3C group started addressing some of these issues with HTTP-NG specification, but it seemed to just die:...]]></description>
        

        <pubDate>Mon, 16 Oct 2006 12:25:52 -0400</pubDate>

        

        <jf:creationDate>Mon, 16 Oct 2006 12:25:52 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 16 Oct 2006 12:25:52 -0400</jf:modificationDate>
        <jf:date>Oct 16, 2006</jf:date>
        <jf:author>Frank Bolander</jf:author>
        <jf:replyCount>0</jf:replyCount>
    </item>


    <item>

        <title>Re: Web 2.0 Communication Layer: from HTTP to Comet to Internet</title>
        <link>http://www.theserverside.com/discussions/thread.tss?thread_id=42641</link>

        

        
            <description><![CDATA[<blockquote>If everyone had an IP address, push would be closer to reality.</blockquote>...]]></description>
        

        <pubDate>Mon, 16 Oct 2006 12:02:28 -0400</pubDate>

        

        <jf:creationDate>Mon, 16 Oct 2006 12:02:28 -0400</jf:creationDate>
        <jf:modificationDate>Mon, 16 Oct 2006 12:02:28 -0400</jf:modificationDate>
        <jf:date>Oct 16, 2006</jf:date>
        <jf:author>Flavio Lima</jf:author>
        <jf:replyCount>6</jf:replyCount>
    </item>



</channel>
</rss>

