4 ms·
Eh, that issue is not really an issue. Server-side functions are actually a surprisingly elegant way of handling security. Basically, instead of calling Users.r
by cmelbye 14y ago
Eh, that issue is not really an issue. Server-side functions are actually a surprisingly elegant way of handling security. Basically, instead of calling Users.remove({}), .insert(), .update(), etc., you create functions on the server that are called from the client. That way, the server controls what you can and can't edit. The end result is still very simple, because you're just calling functions like user_login(), send_message(), etc. instead of operating on the database directly on the client-side.
- drivebyacct2 14y agoYou mean like every other web app in existence ever?
- pygy_ 14y agoYou can call (some) server functions from the client as if they were local. See http://nowjs.com http://nowjs.com for another implementation of the idea.
- arturadib 14y agoAccording to the FAQ they're still working on a built-in user authentication. If you have to implement a separate, server-side CRUD security check by hand, then I don't see why I would choose Meteor over say Rails or Express plus Backbone.
- zquestz 14y agoYou wouldn't get. I use backbone every day for my main job, and it's a great tool. Just imagine when frameworks like Meteor are complete and you can minimize a bunch of your boilerplate code.