271 karma · joined June 16, 2011
When the server receives the request it can simply decrypt the token and deserialize it into some sort of strongly typed usercontext.
I think in terms of development I think its good to have a good idea what's going on end to end, I would consider that normal. However, its good to have a specialism too, that is be a master of one or two things. Its not much to ask someone to be proficient in a programming language or 3 and a database of some description, I don't think.
Thankfully Pocket does the job.
Here's how I lay out my SPA structure : http://anexiledderryman.com/image/50565922110
It seems here we just dive straight into the code.
In particular, I don't like so much coupling of the code and the html together, but that really depends what angle you are coming from, who is the target market of this library.
For example : Take KnockoutJS, it has really good separation of concerns. I really like the MVVM pattern, why? because it means if I have a team of HTML5/CSS design guys, I can let them work off just building good markup and focus on delivering quality static stuff, then my UI developers can work on custom binding handlers for nice CSS3 transition integration and then by C#/Java guys can get their paws wet implementing the data/server functionality without ever treading on each others toes.
I thorughly agree that functional programming concepts are very healthy for a program. Great functional Composability makes reusability and maintainability a dream.
Can't believe this guy is not the only family member to have been hit, insane!
My question is what are the overheads with this kind of organisation, how do you pay your own bills?
Couldn't they even achieve this quickly using Twilio to send SMS token codes to users who opt to have 2 factor auth?
I also recommend the series of digital photography books by Scott kelby, I started with him, was actually this one I found some if very useful: http://www.amazon.co.uk/The-Digital-Photography-Book-Pt/dp/0...
I would say your proposed suggestion is much more limiting, you have basically removed the query string and changed the name.
So your proposed version returns all the data, in most notorious order, that could be tonne of data. You are going to need query strings for paging and filtering and sorting..this is perfectly good api design.
I would recommend odata.org for a read. I would also recommend apigee.com white paper on good api design.
Also with versioning in mind, you may wish too include api/v1.x/mostwanted