# Tangent question regarding Ajax best practice

**URL:** <https://www.ruby-forum.com/t/tangent-question-regarding-ajax-best-practice/191042>\
**Category:** Rails\
**Created:** [July 3, 2010, 12:13pm UTC](https://www.ruby-forum.com/t/tangent-question-regarding-ajax-best-practice/191042 "2010-07-03T12:13:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Doug\_Boude](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/d/74df32/32.png) [@Doug\_Boude](https://www.ruby-forum.com/u/Doug_Boude)\
**Post date:** [July 3, 2010, 12:13pm UTC](https://www.ruby-forum.com/t/tangent-question-regarding-ajax-best-practice/191042/1 "2010-07-03T12:13:02Z")

</div>

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