Re:First chunk of Meteor auth now in GitHub
by blutonium on Saturday June 16, 2012 @05:41AM
(#4120265)
Was it really? Many frameworks don't offer much beyond HTTP basic.
[ Parent
| on HN ]
Re:First chunk of Meteor auth now in GitHub
by tomblomfield on Saturday June 16, 2012 @08:59AM
(#4120552)
The issue with Meteor was that all clients have full write access to the server-side database, including other users' data. Which is problematic, to say the least.
Re:First chunk of Meteor auth now in GitHub
by cmelbye on Saturday June 16, 2012 @03:02PM
(#4121333)
This actually isn't true. One can easily remove the "autopublish" package to disable the behavior of publishing all data to the client, and selectively publish only certain records to the client. Then, all client-side database modification methods can be disabled, and using server-side functions, an authentication system can be built and you can build your application's logic.
Re:First chunk of Meteor auth now in GitHub
by lucian1900 on Saturday June 16, 2012 @06:09AM
(#4120295)
As a consequence of its design, HTTP Basic auth wouldn't have worked as expected with meteor. All it could've done is prevented access to the whole website, users would still be able to see each other's stuff.