Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (athena.apache.org: domain of pharkins@gmail.com designates
 209.85.221.204 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=uBBjKvLjH/Kxbg5BydVkROCW96NJMFvaEzWf9b5LJS7/l+kEa5Mj8CzjUg50PHqY4A
         tHo0EKWBdyfmL89fXRC+gCX4p7iqbGpEC/aNiiIN9cyvLXNsUa+oJClJhIGM/Ty2DDSy
         lSpC7lndV13NRWynWNTBxboRn5CmlTdlUt+so=
MIME-Version: 1.0
In-Reply-To: <20091112185332.GC31986@phare.normalesup.org>
References: <20091112185332.GC31986@phare.normalesup.org>
Date: Thu, 12 Nov 2009 15:22:10 -0500
Message-ID: <66887a3d0911121222x57a6aadclee4e5d264accc3eb@mail.gmail.com>
Subject: Re: AJAX pseudo-push
From: Perrin Harkins <pharkins@gmail.com>
To: Nicolas George <nicolas.george@normalesup.org>
Cc: modperl@perl.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Thu, Nov 12, 2009 at 1:53 PM, Nicolas George
<nicolas.george@normalesup.org> wrote:
> There is an increasingly popular technique to emulate server-initiated push
> over HTTP. I'm sure everyone here knows it well, but for the sake of
> completeness: the clients sends a XMLHttpRequest to the server in the
> background; the server does not answer it immediately, but keeps it for
> later when there is actually something to say to the client; if the request
> timeouts, the client re-sends it.

I think you'd be better off using polling.  There are tools for this
in the popular JS frameworks.

- Perrin