This certainly looks like the best "traditional style" webapp framework yet for node - e.g. something that reminds me strongly of a well-apportioned SpringMVC setup.<p>That said, I'm a huge fan of Meteor. It is (almost) totally non-traditional, but granted it does not give you the fine-grained control of this framework. I can see Hapi being the correct choice if either a) your developers are uncomfortable with large paradigm shifts (and seriously, who can blame them?) or b) you have to conform to a pre-existing API that requires low-level control (which is, of course, a total bummer).<p>Very nice work - and from my skimming of your docs, very nice documentation. Lots of good info in there without a lot of fluff, and I like that it's all on one page. Kudos. I'll definitely try Hapi instead of Connect next time I need something like this.
This looks fantastic. The link to the framework itself is <a href="https://github.com/walmartlabs/hapi" rel="nofollow">https://github.com/walmartlabs/hapi</a>.<p>In particular, I'm excited about the way endpoints are registered:<p><pre><code> // Define the route
var hello = {
handler: function (request) {
request.reply({ greeting: 'hello world' });
}
};
// Add the route
server.addRoute({
method: 'GET',
path: '/hello',
config: hello
});
</code></pre>
This makes it extremely easy to expose API endpoints to internal modules. Let's
say your company has a module related to simple math operations -- exposing this
externally is as simple as adding a 'handler' method.<p><pre><code> var SimpleMath = new function() {
var module = this;
module.divide = function(a, b) {
return a / b;
};
module.multiply = function(a, b) {
return a * b;
};
// Now add the external handler.
module.handler = function(request) {
// somehow access two variables, a and b
request.reply({
product: module.multiply(a, b);
quotient: module.divide(a, b);
});
}</code></pre>
> We also looked at Restify, Tako, and a few others.<p>With the long list of things checked out, I doubt they gave the "few others" a close look. Which is too bad, because Geddy may have been just the ticket.
While I know multitudes of new frameworks are usually unwelcome wheel reinventions, this seems very well done. Kudos to the team.<p>Releasing software like this makes me wonder what other kind of amazing things are going on at Walmart Labs. They have an incredible amount of data about shopping behavior.
One of the guys who is working on this is Eran Hammer, who also co-authored several OAuth specs. He's working on OAuth alternative called Oz (<a href="https://github.com/hueniverse/oz" rel="nofollow">https://github.com/hueniverse/oz</a>).
Played with it a bit last night. Initial impression is it has a much <i>lighter</i> feeling than other frameworks I've tried. Will be diving in deeper for sure.<p>Thanks for releasing this guys!
any comments on how it compares with say Restify (<a href="http://mcavage.github.com/node-restify/" rel="nofollow">http://mcavage.github.com/node-restify/</a>) from folks who have used both ?