Server push is the most efficient and low latency way to exchange data. If both the publisher and the receiver are publicly visible then a protocol such as PubSubHubbub or a simpler Webhook will do the job. However, if the receiver is hidden behind a firewall, a NAT, or is a web-browser which is designed to generated outbound requests, not handle incoming traffic, then the implementation gets harder.

There are two main types of scalability: vertical and horizontal. Vertical scalability consists of potentiating the hardware specs of a given server. This is typically done by increasing the number (and to a minor extent, speed) of the processors, adding more RAM, and so on. Commodity hardware tends to impose a strong limit on the resources that can be augmented. There is only so much that can be stuffed into your typical x64_86 Dell server, even replacing the entire machine with the top of the line model (having the same architecture).

* radiantCMS

* zena

* Comatose

* Adva CMS (Based on Rails Engines)

* zena

Aloha!

This is not the design talk to be afraid of. This is Design with a capital D. Michael Nieling, founder and principal at Ocupop, will be teaching attendees why Design is the single most important aspect of the development process, and how to address these critical concerns with intelligence and an engineer’s unique abilities. Michael, an engineer turned Designer, has experience designing everything from retail kiosks to interactive web applications to iPhone applications.

No, this is not the start of a post where I point and cackle evilly as I explain how the whole "training course" thing was a sham calculated to help me harvest and sell your email addresses to spammers in Katmandu.

I recently came across the interesting-looking Monk framework. It allows you to specify a list of dependencies for technologies to use in your project (in the form of git repositories or gems), and it will take care of extracting them into your application's vendor folder.