I'm going to vent a bit of frustration here. 1. As fast as I learn something, I learn that it has changed or deprecated. Aaargh! 2. I had a suspicion that the singular/plural convention was a lot of silliness and the changes seem to vindicate this view. 3. REST appears to have good intentions, but is generally too limiting in practice and hence requires workarounds that make swiss cheese of the concept. 4. I am worried that the continuous flux as ROR matures is going to mean a short life expectancy for applications. 5. Documentation is abominable or good documentation is scarce.
Frustrations aside I feel much better because you were spot on, Rick D. Responder is a model and qualifying the name resolved the problem. I'm still unclear as to why there was a "name clash" since there is only one class named Responder whether this namespace or elsewhere. But I greatly appreciate all of the the guidance, help and patience from both Ricks'. A little piece of my sanity is in debt to you. Cheers, Bill --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk@googlegroups.com To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
