Home
Jon Phipps's Library tagged → View Popular
Optimizing HTTP headers for ‘ajax’ webapps
...But what about the headers the browser sends?
The size of headers in a basic XHR request:
Firefox3: 495 bytes
IE7: 289 bytes
Safari: 357 bytes
That means if your little ajax request is simply sending 5 bytes, you’re still going to send a few hundred bytes. Wasting time, bandwidth, and processing. For XHR requests, you often simply do not need half of those headers. I already know what the user-agent is, and can send it at the start of the comms if needed. I don’t need an Accept header, because it’s irrelevant. The XHR is going to send back text. etc
We can do a little bit better… Here are the numbers when we add a few lines of js to cut down headers.
URI documentation protocol - Neurocommons
-
How should one go about finding documentation that will explain what a URI names, in cases where this is needed and it is not already at hand? HTTP was not designed to help out here, so the following is not as elegant as would be a protocol designed with this in mind.
If you're doing bulk processing of URI documentation, you may be better off doing bulk downloads or SPARQL queries on an appropriate SPARQL endpoint, as large numbers of probes will be inefficient and will load servers, usually unnecessarily.
The following protocol is designed to be forgiving enough to grandfather many URIs already in use on the Semantic Web, such as those in the RDF Schema vocabulary and Dublin Core, while strict enough to support our URI requirements. It coincides with HTTP in the absence of overrides, responses containing a Location: header, and 200 responses.
Uniform Access to Metadata
-
This document surveys the problem of specifying a uniform method
for obtaining information pertaining to a resource without
necessarily having to parse a representation of the resource. It is an
attempt to rationalise several discussions that have taken place in a
variety of e-mail fora. More background and links to e-mail threads
area available on the wiki
page.
The Self-Describing Web
-
The Web is designed to support flexible exploration of information by human users and by automated agents.
For such exploration to be productive,
information published by many different sources and for a variety of
purposes must be comprehensible to a wide range of Web client software.
HTTP and other Web technologies can be used to deploy resources that are
self-describing, in the sense that only widely available information is necessary for understanding them.
Starting with a URI, there is a standard algorithm that a user agent
can apply to retrieve and interpret a representation of such resources.
Furthermore, when such self-describing resources are linked together, the Web as a whole can support reliable,
ad hoc discovery of information.
This finding describes how document formats, markup conventions, attribute values, and other data formats can be designed to facilitate the deployment of self-describing Web content. -
The Web is designed to support flexible exploration of information, by human users and by automated agents.
For such exploration to be productive,
information published by many different sources and for a wide variety of
purposes must be comprehensible to a wide variety of Web client software.
This finding suggests that there are three strategies that, used in combination, can ensure
such flexible interoperability: 1) where practical, resource representations should be encoded using widely deployed standards; 2) where such widely deployed standards are not sufficient, the encodings used should themselves be described in machine readable form on the Web, using RDF, RDDL, or other standard description systems; and 3) in all cases, each representation should carry information such as media-types, character encoding labels, RDFa, links to specifications, etc. sufficient to support automatic determination of the standards and other specifications necessary for correct interpretation.
To the extent that these guidelines are observed, individual documents become self-describing, in the sense that only widely available information is necessary for understanding them.
Furthermore, when such documents are linked together, the Web as a whole can support reliable,
ad hoc discovery of information.
This finding discusses in more detail the techniques needed to create such a self-describing Web.
URIs, URLs, and URNs: Clarifications and Recommendations 1.0
-
This paper addresses and attempts to clarify two issues
pertaining to URIs, and presents recommendations. Section 1
addresses how URI space is partitioned and the relationship between
URIs, URLs, and URNs. Section 2 describes how URI schemes and URN
namespace ids are registered. Section 3 mentions additional
unresolved issues not considered by this paper and section 4
presents recommendations.
Transparent Content Negotiation in HTTP
-
Transparent Content Negotiation in HTTP Status of this Memo This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited.
Optimizing Page Load Time - die.net
-
It is widely accepted that fast-loading pages improve the user
experience. In recent years, many sites have started using AJAX techniques
to reduce latency. Rather than round-trip through the server retrieving a
completely new page with every click, often the browser can either alter the
layout of the page instantly or fetch a small amount of HTML, XML, or
javascript from the server and alter the existing page. In either case,
this significantly decreases the amount of time between a user click and the
browser finishing rendering the new content.However, for many sites that reference dozens of external objects,
the majority of the page load time is spent in separate HTTP requests for
images, javascript, and stylesheets. AJAX probably could help, but
speeding up or eliminating these separate HTTP requests might help more, yet
there isn't a common body of knowledge about how to do so.While working on optimizing page load times for a high-profile AJAX
application, I had a chance to investigate how much I could reduce latency
due to external objects. Specifically, I looked into how the HTTP client
implementation in common browsers and characteristics of common Internet
connections affect page load time for pages with many small objects.
So how <i>do</i> you code an AJAX Web page?
-
This article introduces you to that practice, the practice of updating Web pages with information from the server. Beyond the XMLHTTP Request object, which has been around for several years as a solution looking for a problem, there is nothing weird needed. Basically, it is how the individual pieces are put together. When they're put together in one way, it is nothing more than a pile of parts; however, when put together in another way, the monster essentially rises from its slab.
HTTP Compression for Web Applications - Intel® Software Network
- the best way to keep the site responsive is to minimize the size of the downloaded pages. Considering the fact that most of the content in a page is textual data, HTTP compression is a promising scheme to improve the response time. Compression algorithms - jonphipps on 2006-07-20
Univeral Resource Identifiers -- Axioms of Web architecture
-
Tim Berners-Lee
Date: December 19, 1996
Status: personal view. Editing status: Italic text is rough. Reques complete edit and possibly massaging, but content is basically there. Words such as "axiom" and "theorem" are used with gay abandon and the reverse - jonphipps on 2006-07-20
Selected Tags
Related Tags
Sponsored Links
Top Contributors
Groups interested in http
-
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
Highlighter, Sticky notes, Tagging, Groups and Network: integrated suite dramatically boosting research productivity. Learn more »
Join Diigo