| /** | |
| Code copyright Dustin Diaz and Ross Harmes, Pro JavaScript Design Patterns. | |
| **/ | |
| // Constructor. | |
| var Interface = function (name, methods) { | |
| if (arguments.length != 2) { | |
| throw new Error("Interface constructor called with " + arguments.length + "arguments, but expected exactly 2."); | |
| } | |
| this.name = name; |
| <!DOCTYPE html> | |
| <html> | |
| <head> | |
| <meta charset="utf-8"> | |
| <title>example crossroads + hasher</title> | |
| <meta name="viewport" content="width=device-width, initial-scale=1.0"> | |
| </head> | |
| <body> | |
| <div id="wrapper"> | |
| <ul> |
| license: gpl-3.0 |
| Backbone.BaseCollection = Backbone.Collection.extend({ | |
| // Holds id of locally deleted items we ignore if we | |
| // 'freshen' the collection and changes haven't propagated yet. | |
| _localDeletedIds: [], | |
| // Take an array of raw objects | |
| // If the ID matches a model in the collection, set that model | |
| // If the ID is not found in the collection, add it | |
| // If a model in the collection is no longer available, remove it | |
| // | |
| // Keeps local changes, in case we've added things in the meantime. |
This article has been given a more permanent home on my blog. Also, since it was first written, the development of the Promises/A+ specification has made the original emphasis on Promises/A seem somewhat outdated.
Promises are a software abstraction that makes working with asynchronous operations much more pleasant. In the most basic definition, your code will move from continuation-passing style:
getTweetsFor("domenic", function (err, results) {
// the rest of your code goes here.
| # Installing graphite dependencies | |
| apt-get install -y python2.6 python-pip python-cairo python-django python-django-tagging | |
| apt-get install -y libapache2-mod-wsgi python-twisted python-memcache python-pysqlite2 python-simplejson | |
| pip install whisper | |
| pip install carbon | |
| pip install graphite-web | |
| # Setup a vhost by grabbing the example the graphite team released on their repo. | |
| # In this file, you'll provide the url used to access to your Graphite dashboard | |
| wget https://raw.github.com/tmm1/graphite/master/examples/example-graphite-vhost.conf -O /etc/apache2/sites-available/graphite |
| var _missing= function(data){ return React.DOM.pre(null, "Route not found: "+ data.route) }, | |
| _router= null, | |
| _started= false, | |
| _nextId= 1; | |
| function handleRouteChange(container, component) { | |
| var routeParams= Array.prototype.slice.call( arguments, 1 ) | |
| React.renderComponent( | |
| component({ routeParams:routeParams }, null), | |
| container |
There are a lot of ways to serve a Go HTTP application. The best choices depend on each use case. Currently nginx looks to be the standard web server for every new project even though there are other great web servers as well. However, how much is the overhead of serving a Go application behind an nginx server? Do we need some nginx features (vhosts, load balancing, cache, etc) or can you serve directly from Go? If you need nginx, what is the fastest connection mechanism? This are the kind of questions I'm intended to answer here. The purpose of this benchmark is not to tell that Go is faster or slower than nginx. That would be stupid.
So, these are the different settings we are going to compare:
This tutorial uses the "Sample hapi.js REST API" project.
Take a look at: https://github.com/agendor/sample-hapi-rest-api/
##Topics