continuous development

In contrast to continuous integration, continuous development, at the example of Ruby language is simply dreadful. Today I spent quite some time trying to figure out combination of interpreter and gems to match completely undocumented example of 2nd genneration Juggernaut from called blossom.

Anyway. It looks like new Juggernaut (again almost no documentation at all) implements "whatever is available" strategy for selecting reverse-AJAX channel technology. It can be using websockets, server-generated events, some IE speciality and finally in the worst case Flash TCP connectivity. No success yet in starting it up though. Need some time to digest sources of new Juggernaut.

This approach goes bit along the lines of the concept of liquid services (presented by Daniele Bonetta) adjusting to available infrastructure.

No comments:

Post a Comment