NodeJS Meetup Tonight!

[chrismatthieu]

Attention Phoenix Node.JS and Javascript Developers: Join us for geeky
nodejs discussions tonight at 7PM at UAT in room 245!

Tonight's agenda includes recaps from !Conf and JSConf as well as
maybe a discussion about Meteor (http://meteor.com/screencast). Let
me know if you have any other discussion topics or projects that you
would like to share with the group tonight!

Hack the Planet!
Chris Matthieu

[David Rauschenbach]

Notice to attendees:

If you are in independent contractor with availability, I will be
attending this evening specifically to find help for a project I am
involved with.

David

> --
> NodeAZ - node.js Users Group of Arizona
> http://groups.google.com/group/nodeaz/
> Twitter: @nodeaz

[David Rauschenbach]

Here's a quote I just read, about one of Meteor's key innovations:

 

Sandro Pasquali writes:

 

I think the key architectural novelty is the idea of *only* updating the canonical model (the one on the server, usually a database). Compose db commands on the client, those change the server model, clients are informed that the model has changed, templates (etc) are updated. This is new.

 

Other application frameworks work on the idea of keeping a local representation of data, updating that, then saving it (via XHR usually, a POST). It is up to you to write the "boilerplate" for checking the freshness of that local data.

 

So the idea is interesting and works to solve a known situation.

 

(excerpt from http://www.quora.com/Meteor-web-framework/Whats-cool-about-Meteor)

 

I have to agree with this. Without this innovation, I post fat and complete records to a REST endpoint, then in that endpoint handler I load another fat complete record from Mongo, and then walk the keys, updating one model from the other, then I let Mongoose turn the diff into a selective Mongo update query consisting of the diff values only. The whole REST endpoint, and all the data transfer of unchanged data, does not make a whole lot of sense, if only a single field on some form is changing state.

 

That post goes on to list many interesting disadvantages of the current "preview" release of Meteor, such as the exposure of your full DB to the internet, which the authors of Meteor say they are already addressing, since they are not exactly dummies, and the current release is, after all, just a preview.

 

All in all, I like it a lot. I'll hold out for Jade support tho.

 

David

 

 

On Mon, Apr 16, 2012, at 08:51 AM, chrismatthieu wrote: