Friday, July 2, 2010
In my current project, I'm finding myself really adding meat to my global ajax responders (the global code that typically is used to indicate that some ajax activity is taking place). This is really the first time it has seemed like the right place for me to add a lot of logic, but in doing so it got me to wondering if I really SHOULD be doing this. Reason being, my global responder is going to respond "globally" to ANY ajax activity, and the logic I'm writing will only apply to SOME of the ajax activity (in this case, some = most, but not all).
How does it strike you all who use global responders? Is it just a bad road to go down to add logic that only applies to certain ajax calls in a global responder?
Thanks for your thoughts.
Doug Boude
--
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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment