Although the XMLHttpRequest has the capability of making a DOM
available from the resulting text, the client and server don't have to
make use of it. One could take the responseText and pass it to eval()
if the other end sent JSON. A BEEP API should support any valid use of
BEEP, just as XMLHttpRe
On 2-Nov-06, at 5:05 AM, Dave Raggett wrote:
well how about an XMLBEEPRequest specification then?
Beep is kind of like a bidirectional version of HTTP and includes
multiplexing capabilities with stream prioritization, see:
http://beepcore.org/index.html
Beep isn't in widespread use a
On 2-Nov-06, at 4:48 AM, Anne van Kesteren wrote:
FYI: The list for raising issues on XMLHttpRequest is public-
[EMAIL PROTECTED]
Thanks, I'll bring up the topic there as well. Changing
the policy on browser connection limits is lightweight
enough, though, that whatwg could be very effective
On Thu, 2 Nov 2006, Anne van Kesteren wrote:
FYI: The list for raising issues on XMLHttpRequest is [EMAIL PROTECTED]
On Wed, 01 Nov 2006 17:34:24 +0100, Ted Goddard <[EMAIL PROTECTED]>
wrote:
[...]
I would like to propose that the HTTP connection limit
be standardized at two per user-initia
FYI: The list for raising issues on XMLHttpRequest is [EMAIL PROTECTED]
On Wed, 01 Nov 2006 17:34:24 +0100, Ted Goddard <[EMAIL PROTECTED]>
wrote:
[...]
I would like to propose that the HTTP connection limit
be standardized at two per user-initiated window. (For
instance, Safari is not limit
On 1-Nov-06, at 4:42 PM, Charles Iliya Krempeaux wrote:
Hello,
I think we're starting to see some of the limits of HTTP being hit.
We're actually quite far from using the full capabilities
of HTTP. We're definitely bumping into limits exposed by
HTTP implementations, though (in the case of
Hello,I think we're starting to see some of the limits of HTTP being hit.Personally, I'd like to a protocol which allows communication in both ways.HTTP 1.2? XMPP/Jabber? Something else?
See yaOn 11/1/06, Ted Goddard <[EMAIL PROTECTED]> wrote:
Ajax applications often make use of multiple concurre
Ajax applications often make use of multiple concurrent
HTTP requests; in particular Ajax Push (Comet/Reverse Ajax)
makes use of two HTTP connections: one to block waiting for
messages from the server, the other to send messages to
the server.
The problem is that the connection limit for many br
