mailto Protocol msdn.org
The mailto URL scheme RFC 2368 ietf.org
HTML Tables with CSS Styles textfixer.com
W3C Device APIs
Device APIs Working Group w3.org
HTML5
The Future HTML5 software.intel.com, 9/2013
[investigate asm.js: ~2x javascript overhead vs. native optimized code, compared to typical ~5x overhead of javascript]
Geolocation API Specification w3.org
HTML5 geolocation w3schools.com
Chrome
Chrome DevTools developers.google.com
Chrome command line switches src.chrome.com
Default stylesheet
Chrome DevTools - Settings developers.google.com
[The default stylesheet for Chrome Portable is here: ]
...\Chrome\latest_release\Profil\Default\User StyleSheets\Custom.css
session ID wikipedia.org
Session tracking [jsessionid] ibm.com, iSeries infocenter
Java Servlet 3.1 specification oracle.com
Session Tracking Mechanisms
Cookies
Session tracking through HTTP cookies is the most used session tracking mechanism and is required to be supported by all servlet containers. The container sends a cookie to the client. The client will then return the cookie on each subsequent request to the server, unambiguously associating the request with a session. The standard name of the session tracking cookie must be JSESSIONID. Containers may allow the name of the session tracking cookie to be customized through container specific configuration.
SSL Sessions
Secure Sockets Layer, the encryption technology used in the HTTPS protocol, has a built-in mechanism allowing multiple requests from a client to be unambiguously identified as being part of a session. A servlet container can easily use this data to define a session
URL Rewriting
URL rewriting is the lowest common denominator of session tracking. When a client will not accept a cookie, URL rewriting may be used by the server as the basis for session tracking. URL rewriting involves adding data, a session ID, to the URL path that is interpreted by the container to associate the request with a session. The session ID must be encoded as a path parameter in the URL string. The name of the parameter must be jsessionid. Here is an example of a URL containing encoded path information:
http://www.myserver.com/catalog/index.html;jsessionid=1234
URL rewriting exposes session identifiers in logs, bookmarks, referer headers, cached HTML, and the URL bar. URL rewriting should not be used as a session tracking mechanism where cookies or SSL sessions are supported and suitable
Apache Tomcat 7 - Clustering/Session Replication HOW-TO tomcat.apache.org
Clustering and Load Balancing in Tomcat 5, Part 1 2004, onjava.com
HTTP PATCH
RFC 5789 - PATCH Method for HTTP tools.ietf.org
Edge Rails: PATCH is the new primary HTTP method for updates weblog.rubyonrails.org
URLs
Naming and Addressing: URIs, URLs, ... w3.org/Addressing
Uniform Resource Locators (URL) w3.org/Addressing/URL
Content-ID cid: URL
Content-ID and Message-ID Uniform Resource Locators | RFC2392 ietf.org
- obsoletes RFC2111
Usability [um why is this here?
Else
Difference between close_wait and time_wait j2eedebug.blogspot.com
Justice Will Take Us Millions Of Intricate Moves Leonard Richardson, Presentation at QCon conference, San Francisco. crummy.com. 20 Nov 2008.
Discussion of web protocols
Evolvability w3.org Tim Berners Lee
Cool URIs Don't Change w3.org Tim Berners Lee 1998
Architecture of the World Wide Web, Volume One w3.org
Includes design principles and best practices
Tiggr gotiggr.com
Hosted interactive web and mobile HTML prototypes
Web Hypertext Application Technology Working Group | WHATWG whatwg.org
Web Applications 1.0 whatwg.org/specs/web-apps
This is essentially HTML5 as specified by WHATWG
HTML whatwg.org/specs/web-apps
This is the 'HTML Living Standard' as specified by WHATWG