Note that there are some explanatory texts on larger screens.

plurals
  1. USMike Clymer
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. COTrek, you are spot on with your analysis of using Backbone in apps with extended usage patterns, and complex state management. I went through the experience of converting a legacy app over to Backbone and had to do exactly what you listed. We needed to integrate Marionette as well as write plenty of glue code for things like pre/post route filtering, memory leak mitigation, and better event management.
      singulars
    2. COThis should be accepted as the answer by the OP. It is the most correct response to the question. @jason-harrelson is spot-on by saying that persistence is not needed to support the intended use of POST. The nice part about using POST, for a search resource, is the ability to use this as a future feature like saved searches, or suggested searches for a user of your API.
      singulars
    3. COPeder, I appreciate what Rails 3.1 is doing with ActiveModel::SecurePassword. It promotes the use of bcrypt, which is a good thing. AFAIK, it is relatively easy to configure Devise to use bcrypt as its encryption mechanism. Migrating existing users can create issues, but that is another topic. ActiveModel::SecurePassword doesn't actually provide a robust auth framework that includes features like role integration, email verification, remember me tokens, and multiple auth account management. I see no reason to roll my own, when I can get all of these features and make use of bcrypt in Devise.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload