Facebook Twitter

Electronic Frontier Foundation. Spray: Akka smells HTTP. Spray spray is a suite of lightweight Scala libraries providing client- and server-side REST/HTTP support on top Akka.

Spray: Akka smells HTTP

We believe that, having chosen Scala (and possibly Akka) as primary tools for building software, you’ll want to rely on their power not only in your application layer but throughout the full (JVM-level) network stack. spray provides just that: a set of integrated components for all your REST/HTTP needs that let you work with idiomatic Scala (and Akka) APIs at the stack level of your choice, all implemented without any wrapping layers around “legacy” Java libraries. Principlessprays development is guided by the following principles: Fully asynchronous, non-blockingAll APIs are fully asynchronous, blocking code is avoided wherever at all possible.

Actor- and Future-basedspray fully embraces the programming model of the platform it is built upon. High-performanceEspecially sprays low-level components are carefully crafted for excellent performance in high-load environments. OkHTTP: Alright SPDY. OkHTTP HTTP is the way modern applications network.

OkHTTP: Alright SPDY

It’s how we exchange data & media. Doing HTTP efficiently makes your stuff load faster and saves bandwidth. OkHttp is an HTTP client that’s efficient by default: SPDY support allows all requests to the same host to share a socket. OkHttp perseveres when the network is troublesome: it will silently recover from common connection problems. You can try OkHttp without rewriting your network code. OkHttp supports Android 2.2 and above. RESTHook: Rest Assured, Get Hooked.

RESTHooks REST Hooks itself is not a specification, it is a collection of patterns that treat webhooks like subscriptions.

RESTHook: Rest Assured, Get Hooked

These subscriptions are manipulated via a REST API just like any other resource. That’s it. Really. Stop the polling madness With most modern REST APIs, polling is the only way to detect changes. Go beyond webhooks Webhooks are great, but really hard for users to setup. Peace, love and REST. HttpFS: HDFS over HTTP. HttpFS[ HttpFS is a server that provides a REST HTTP gateway supporting all HDFS File System operations (read and write).

HttpFS: HDFS over HTTP

And it is inteoperable with the webhdfs REST HTTP API. HttpFS can be used to transfer data between clusters running different versions of Hadoop (overcoming RPC versioning issues), for example using Hadoop DistCP. HttpFS can be used to access data in HDFS on a cluster behind of a firewall (the HttpFS server acts as a gateway and is the only system that is allowed to cross the firewall into the cluster). HttpFS can be used to access data in HDFS using HTTP utilities (such as curl and wget) and HTTP libraries Perl from other languages than Java.

The webhdfs client FileSytem implementation can be used to access HttpFS using the Hadoop filesystem command (hadoop fs) line tool as well as from Java aplications using the Hadoop FileSystem Java API. Nweb: a tiny, safe Web server (static pages only) Introduction Have you ever wanted to run a tiny, safe web server without worrying about using a fully blown web server that could be complex to install and configure?

nweb: a tiny, safe Web server (static pages only)

Do you wonder how to write a program that accepts incoming messages with a network socket? Have you ever just wanted your own Web server to experiment and learn with? Further updates in 2012 to support recent web-server and browser standards and a code refresh. Well, look no further -- nweb is what you need. This article covers: What the nweb server program offersSummary of C functions features in the programPseudo code to aid understanding of the flow of the codeNetwork socket system calls used and other system callsHow the client side operatesC source code. Best Practices for Speeding Up Your Web Site.

The Exceptional Performance team has identified a number of best practices for making web pages fast.

Best Practices for Speeding Up Your Web Site

The list includes 35 best practices divided into 7 categories. Minimize HTTP Requests tag: content 80% of the end-user response time is spent on the front-end. Most of this time is tied up in downloading all the components in the page: images, stylesheets, scripts, Flash, etc. One way to reduce the number of components in the page is to simplify the page's design. Combined files are a way to reduce the number of HTTP requests by combining all scripts into a single script, and similarly combining all CSS into a single stylesheet. CSS Sprites are the preferred method for reducing the number of image requests. Image maps combine multiple images into a single image. Inline images use the data: URL scheme to embed the image data in the actual page. Cosign: web single sign-on. WebHooks. HTTP Made Really Easy.

A Practical Guide to Writing Clients and Servers Home > Web Technology Made Really Easy > HTTP Made Really Easy Donate Table of Contents|Footnotes December 10, 2012-- Updated the links about robots.

HTTP Made Really Easy

HTTP is the network protocol of the Web. This tutorial explains the simple, English-based structure of HTTP communication, and teaches you the practical details of writing HTTP clients and servers. Since you're reading this, you probably already use CGI. The whole tutorial is about 15 printed pages long, including examples. Before getting started, understand the following two paragraphs: Writing HTTP or other network programs requires more care than programming for a single machine.

OK, enough of that. Top of Page.