Kenyth Zeng's Library tagged → View Popular
URLFetch 5 second timeout - GDocs Feeds Aren't Working - Google App Engine | Google Groups
-
Because of the 5 second timeout limitation for URLFetch
13 Nov 09
Chromium Blog: A 2x Faster Web
-
It is designed specifically for minimizing latency through features such as multiplexed streams, request prioritization and HTTP header compression.
27 Sep 09
HTTP/1.1: Method Definitions
-
it is possible that a sequence of several requests is non-
idempotent, even if all of the methods executed in that sequence are
idempotent. -
This method allows the client to
determine the options and/or requirements associated with a resource,
or the capabilities of a server, without implying a resource action
or initiating a resource retrieval. - 6 more annotations...
20 Sep 09
NginxHttpCoreModule
-
-
~*for case insensitive matching -
~for case sensitive matching
To use regular expressions, you must use the a prefix:
-
-
the prefix "=", which matches an exact query only.
- 6 more annotations...
25 Aug 09
TerrorZone: File (MIME) Types (Web Design in a Nutshell, 2nd Edition)
-
The browser determines how to handle the file based on that
information -- whether to display the contents in the window, or
to launch the appropriate plug-in or helper application. -
MIME
(Multipurpose Internet Mail Extension), which was originally
developed for sending attachments in email. - 2 more annotations...
18 Jun 09
Communicating with a Server - Google Web Toolkit - Google Code
-
GWT allows only asynchronous
server calls. When sending an HTTP request, the client code must register a callback method that will handle the response (or the error, if the call fails). -
<inherits name="com.google.gwt.http.HTTP" />
HTTP/1.1 Keep-Alive header
-
The Keep-Alive field is NOT a standard HTTP header field and may not be supported by all clients.
Apache Tomcat Configuration Reference - The HTTP Connector
-
If the
PATH(Windows)orLD_LIBRARY_PATH(on most unix system)
environment variables contain the Tomcat native library, the APR connector
will automatically be configured. -
The default value is to use the value that has been set for the
connectionTimeout attribute. - 2 more annotations...
Apache Tomcat 6.0 - Connectors How To
-
When using a single server, the performance when using a native webserver in
front of the Tomcat instance is most of the time significantly worse than a
standalone Tomcat with its default HTTP connector, even if a large part of the web
application is made of static files.
17 May 09
page 6 > Asynchronous HTTP and Comet architectures - JavaWorld
-
The long poll is one of the two Comet strategies to reduce the frequency of HTTP calls
-
The second Comet strategy is response body streaming.
- 6 more annotations...
page 3 > Asynchronous HTTP and Comet architectures - JavaWorld
-
streaming doesn't mean that the data will be read or written directly to the network. All read and write operations work on internal
socket buffers. When a write method is called, the operating system kernel transfers the data to the socket'ssendbuffer. Returning from the write operation just says that the data has been copied to this low-levelsendbuffer. It doesn't say that the peer has received the data. -
Unfortunately, the
current Servlet API 2.5 supports neither non-blocking data streaming nor asynchronous message handling. - 3 more annotations...
page 2 > Asynchronous HTTP and Comet architectures - JavaWorld
-
broken into several TCP segments when sent.
-
Data transfer fragmentation can be hidden at the API level by accessing the body data as a steady and continuous stream. This
approach, known as streaming, avoids the need to buffer large chunks of data before processing it. Streaming can also reduce
the latency of HTTP calls, especially if both peers support streaming. - 1 more annotations...
page 1 > Asynchronous HTTP and Comet architectures - JavaWorld
-
In this article I introduce asynchronous, non-blocking HTTP programming and explain how
it works. -
Asynchronous message handling also enables HTTP pipelining, which you can use to send multiple HTTP requests without waiting for the server response to former requests. The response
messages will be returned by the server in the same order as they were sent. Pipelining requires that the underlying HTTP
connection is in persistent mode, which is the standard mode with HTTP/1.1. - 1 more annotations...
16 May 09
Comet Daily » Blog Archive » Comet and HTTP Pipelining
-
duplex communication in HTTP based on request content streaming in XHR requests. A request could use “chunked” transfer encoding, and progressively send parts of the request body. While the client streaming of the request body is taking place, the response could then be returned to the user agent and also stream data for the response body.
-
being able to handle the response after sending part of the request, but prior to finish sending the entirety of the request.
- 6 more annotations...
Selected Tags
Related Tags
Sponsored Links
Ads by Google
Top Contributors
Groups interested in http
Related Lists on Diigo
-
Apache HTTP Server
Collection of websites abou...
Items: 17 | Visits: 41
Created by: Ray Metzen
-
web development
Items: 1 | Visits: 1
Created by: damnit damnit
Diigo is about better ways to research, share and collaborate on information. Learn more »
Join Diigo
