…the front-end, and Rails 2.3, Postgres, memcached, redis, resque, and for websockets Sinatra, and a few other things. The front-end is communicating with the back-end via a JSON API.
I've come to the realization that this much client-side processing and decoupling is detrimental to both the speed of development, and application performance (a ton of JavaScript has to be loaded and evaluated each time you fire up the app). It's better to let the server handle HTML rendering …
…URLRequest, URLRequestContext, and URLRequestJob implementations net/ websockets WebSockets protocol implementation
Each of the above makes for a great read for the curious - the code is well documented, and you'll find plenty of unit tests for every component.
Architecture and performance on mobile platforms # โ
Mobile browser usage is growing at an exponential rate and even by modest projections, it will eclipse desktop browsing in the not so distant future. …
…applications to take over the client socket and perform arbitrary operations on it, e.g. implementing WebSockets, streaming data to the client, etc.
Did Rack not support streaming? Actually yes it did, you can do it by returning a body object that outputs body chunks in the # each method, as explained in our past article Why Rails 4 Live Streaming is a Big Deal . But this API is a bit clunky. The socket hijacking API provides access to a Ruby IO object-like API.
Support …
Your browser is one of the most and best instrumented development platforms - you may just not realize it yet. Of course, you can inspect the source, walk the DOM, fiddle with the CSS, and evaluate and debug your JavaScript, but there is so much more! Granted, there is always room for improvement, but the exciting part is that much of this functionality is also built with the same technology we build our sites: HTML, CSS, JavaScript, and WebSockets. This means we can extend it, leverage …
…by writing better components. For example, we just released universal login buttons that talk over WebSockets and are wired into the users table of the app's database. Since Markdown is increasingly ubiquitous for writing content, it's going to be part of the Meteor toolchain. I wouldn't be surprised if we end up releasing a component like Stack Overflow's editor , with the full " Meteor" standard of code quality, so that no one has to roll their …
Evented I/O allows us to support non-HTTP protocols in the future, e.g. WebSockets.
It should be noted that to fully enjoy the benefits of evented I/O, your web server must also be able to support high I/O concurrency. Nginx and Phusion Passenger Standalone already support this by default. On Apache you may have to increase your number of processes or worker threads. If you really need a lot of I/O concurrency then we recommend you to use the worker MPM.
It should also be noted that …
…allows Node.js to serve all TCP traffic, including HTTP and WebSockets. If you have a solo instance, little additional configuration is needed. On a cluster, your WebSocket backend must have a shared socket store: we do not currently have sticky sessions between application instances. If you're using socket.io , it includes a RedisStore option for just this case. We'll be improving and simplifying WebSocket support as we collect more information from our customers. …
…applications for Socket.IO and Engine.IO , a new implementation of Websockets and their alternative browser-server connection mechanisms that promise to ease some of the difficulty of working with Websockets. A couple of talks demonstrated how to combine Socket.IO with Browserify , SubStack's browser adaptor layer for Node code. Seeing Socket.IO combined with a multiplexer in the browser to allow multi-channel communication over a single connection …
With the advent of new standards and technologies such as HTML5, Websockets, 0MQ, rich web applications and client side frameworks such as Backbone, Spine and Emberjs. There's more choice to create layers of grouped services and consumers of them.
If there's one place you should be iterating quickly it's the point in which the user touches and interacts with your application. What the users sees, how they see it and how it fulfils their needs.
James Coglan : A History of Websockets
Stuart Eccles : Conan the deployer - capistrano extensions focussing on AWS
Richard Livsey : Something on MonogoDB or something on removing authentication from your models (separation of concerns)
Harry Marr : Custom documentation generators ( example )
Chris Parsons : The crowd-sourced talk. One slot at these evenings is given over to someone prepared to do a talk on something that the …