In my last couple of blog posts I showed you can use a couple of the new HTML5 related APIs (webrtc, web workers, device orientation) directly from your browser. A couple of days ago I ran into the W3C Vibration API, which reached "Candidate Recommendation" status last week (8th of May).

I've been experimenting with web workers and the various browser implementations. Most of the articles I've seen show an example where a single worker thread is started in the background to execute some heavy task. This frees up the main thread to render the rest of the webpage and respons to user input.

Yesterday I gave a presentation at JPoint's meetingpoint on how to get your API or service from using the basic REST principles such as verbs and resources to a complete RESTful service that fully supports "Hypermedia as the engine of application state" (HATEOAS).

I've just put the slides on slideshare if you want to see what I talked about:

In my previous article I showed how to use box2d-web and deviceorientation to rol around a set of circles using standard HTML5 APIs. My initial goal of that article was to load in an image, translate it to a series of seperate circles, and let you play around with that. But that's for later.

When the first smartphones came out, they all had the traditional labyrinth applications. Application where you had to move a ball around a certain path by tilting and moving your phone around. There is also an HTML5 specification that allows you to do this directly from your browser. This would allow us to create all kind of cool games that run directly from the browser.

When you have many services it is a good thing to register them somewhere so your consumers can easily find them, see what they are about, determine whether the service levels are good enough etc. When you look back at the heyday of SOA everyone was pusing registries (or repositories, but that terminology is a different subject).

Most people have already heard about SPDY, the protocol, from google, proposed as a replacement for the aging HTTP protocol. Webservers are browsers are slowly implementing this protocol and support is growing. In a recent article I already wrote about how SPDY works and how you can enable SPDY support in Jetty.

In a recent article I showed how you can use webrtc, canvas and websockets together to create a face detection application whose frontend runs completely in the browser, without the need for plugins. In that article I used a Jetty based backend to handle the image analysis using OpenCV through the JavaCV wrapper.

In this article we'll look at how you can connect from Scala to RabbitMQ so you can support the AMQP protocol from your applications. In this example I'll use the Play Framework 2.0 as container (for more info on this see my other article on this subject) to run the application in, since Play makes developing with Scala a lot easier.