On 5/15/06, Jeff Rush <[EMAIL PROTECTED]> wrote:
I got the definition from Wikipedia:
http://en.wikipedia.org/wiki/AJAX
"Ajax, shorthand for Asynchronous JavaScript+CSS+DOM+XMLHttpRequest, is a Web
development technique for creating interactive web applications."
From the page of the guy tha
Jeff Rush wrote:
> Benji York wrote:
>> Jeff Rush wrote:
>>
>>> Just checking if I'm missing something -- with the removal of HTTP
>>> streaming/chunking in 3.2, this means that the async bi-directional
>>> persistent socket communications associated with Ajax is NOT
>>> possible at this time?
>>
>
Zachery Bir wrote:
I think Benji's commenting on the fact that you're creating a
synchronous connection when you hold it open like that.
Exactly. As Jean-Marc noted, Jeff's talking more about "streaming" than
"asynchronicity" (is that a word?).
FWIW, I've been using MochiKit's Async packag
Jeff Rush wrote:
Just checking if I'm missing something -- with the removal of HTTP
streaming/chunking in 3.2, this means that the async bi-directional
persistent socket communications associated with Ajax is NOT possible
at this time? That a request/response must quickly run to completion
on
On May 15, 2006, at 1:23 PM, Jeff Rush wrote:
Benji York wrote:
Jeff Rush wrote:
Just checking if I'm missing something -- with the removal of
HTTP streaming/chunking in 3.2, this means that the async bi-
directional persistent socket communications associated with Ajax
is NOT possible at
Benji York wrote:
Jeff Rush wrote:
Just checking if I'm missing something -- with the removal of HTTP
streaming/chunking in 3.2, this means that the async bi-directional
persistent socket communications associated with Ajax is NOT possible
at this time?
Don't know if it is or isn't, but tha
Jeff Rush wrote:
Just checking if I'm missing something -- with the removal of HTTP
streaming/chunking in 3.2, this means that the async bi-directional persistent
socket communications associated with Ajax is NOT possible at this time?
Don't know if it is or isn't, but that's a novel definitio
Jeff Rush wrote:
> Just checking if I'm missing something -- with the removal of HTTP
> streaming/chunking in 3.2, this means that the async bi-directional
> persistent socket communications associated with Ajax is NOT possible
> at this time? That a request/response must quickly run to completio
Just checking if I'm missing something -- with the removal of HTTP
streaming/chunking in 3.2, this means that the async bi-directional persistent
socket communications associated with Ajax is NOT possible at this time? That
a request/response must quickly run to completion on a thread and canno
