Alexander Beletsky

Seems like very useful link, would you like to try it out and contribute it to this proj?

hey @mic0331 1. Thanks for pointing to `backbone.basicauth` - looks like nice plug. Anyway, the solution by @Vijar a bit more, since it's very simple and actually delegating setting auth...

After a bit while, I don't think it's possible. Some good input from Vinay. > A few points: > Basic auth in itself provides no logout, since it just passes...

> The only concern it looks like is to hope that some one isn't able to grab the token before it expires. Even if they do, they only have max...

I really like Github OAuth implementation with issuing access tokens and then using those are request query param, like `https://api.github.com/users/alexanderbeletsky/starrted?access_token=e133dj90xu312...`, it simple and works nice.

I never worked with that, unfortunately. Will you be able to contribute that section?

I think both options are cool, depending of the needs. And both could be described in [Deployment](https://github.com/alexanderbeletsky/backbone-express-spa#deployment) section in README. @Muscula would you consider to contribute CDN deployment best practice?...

My rule of thumb is - the name of file, corresponds to the name of `exported entity`. - If file defines a module (js object), like `viewManager`, filename - `viewManager.js`....

[Here](http://ricostacruz.com/backbone-patterns/#file_naming) I can see 'flat' convetion style. So, files are simply `views/mainview.js`, `models/task.js`, `collections\contacts.js` etc. It makes sense to me, actually. What do you think?

I've seen in on the last JavaScript weekly issue and it looks attractive. But for this boiler-plate I would probably try to keep as 'less-frameworks-used' as possible. Jasmine + PhantomJS...