Clean URIs are one component of a clean website, and it is an important one. The majority of end-user access to the Internet involves a URI, and whether or not the user actually enters the URI, they are working with one nonetheless.

WebTest has an easy syntax with steps having meaningful names that can be understood even when you don't know WebTest. Additionally, the recorder allows you to quickly generate a first draft of your tests that you can adapt and refactor to build robust tests suites. Don't forget: capture/replay is the least cost-effective way of automating test cases!

noVNC is a VNC client implemented using HTML5 technologies, specifically Canvas and WebSocket (supports 'wss://' encryption).
For browsers that do not have builtin WebSocket support, the project includes web-socket-js, a WebSocket emulator using Adobe Flash .
In addition, as3crypto has been added to web-socket-js to implement WebSocket SSL/TLS encryption, i.e. the "wss://" URI scheme.

You can use any of the Stomp Clients to work with any JMS compliant message broker, for example HornetQ. There are Stomp clients for many languages, and Stomple adds JavaScript via WebSockets. This means that you can send and receive JMS messages directly in the browser (when it supports WebSockets).

One challenge with using XMLHTTPRequest is that browsers behave differently when it comes to streaming of content. A common complaint against XMLHTTPRequest in IE was that it doesn’t stream content. More specifically, the responseText property cannot be queried when readyState=3 (Receiving) and it only becomes available when readyState=4 (Loaded). This means that while your JavaScript will know when the transfer of the response body starts, you must wait for the response to complete before examining it. If your goal is to stream down a "never-ending" stream of data, you'll find that IE's XHR object never gets to the Loaded readyState and thus you cannot examine the "partial" response.

A Node.js server for forwarding webhook requests in a non-blocking manner. http://www.webhooks.org/ are brilliant, but implementing them as a provider is a little tricky as your application has to make HTTP request to arbitrary endpoints when specific actions occur. If there are many of those endpoints and some of them are slow to respond, this could degrade the performance of your application. A common solution to this problem is to place outgoing webhook requests in a queue. webhook-relay is a self-contained queue and response sending agent. You send it an HTTP POST describing the webhook request that needs to be sent, it replies instantly with an "OK", and the request itself is sent off shortly afterwards.

If you manage the infrastructure that sits behind a high traffic application you don't want any surprises. You want to understand your breaking points, define your capacity thresholds, and know how to react when those thresholds are exceeded. Testing the production infrastructure with actual anticipated load levels is the only way to understand how things will behave when peak traffic arrives.

Doloto is an AJAX application optimization tool, especially useful for large and complex Web 2.0 applications that contain a lot of code, such as Bing Maps, Hotmail, etc. Doloto analyzes AJAX application workloads and automatically performs code splitting of existing large Web 2.0 applications. After being processed by Doloto, an application will initially transfer only the portion of code necessary for application initialization.

Allows you to upload files using HTML5 Gears, Silverlight, Flash, BrowserPlus or normal forms, providing some unique features such as upload progress, image resizing and chunked uploads.