# Prevent a click happy user?

**URL:** <https://www.ruby-forum.com/t/prevent-a-click-happy-user/128644>\
**Category:** Rails\
**Created:** [February 9, 2008, 8:11pm UTC](https://www.ruby-forum.com/t/prevent-a-click-happy-user/128644 "2008-02-09T20:11:40Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![rickf](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/r/9e8a1a/32.png) [@rickf](https://www.ruby-forum.com/u/rickf)\
**Post date:** [February 9, 2008, 8:11pm UTC](https://www.ruby-forum.com/t/prevent-a-click-happy-user/128644/1 "2008-02-09T20:11:40Z")

</div>

Hello,

So a product I have been working on is in SQA and they have uncovered  
what is considered a defect in my implementation. I should point out  
that navigation is link based via a drop down CSS menu.

Essentially the tester clicks a ton of links after issuing a post to the  
server. The browser queues up all the requests but the result is the  
browser slows down in behavior until the code catches up (if that makes  
any sense).

Do folks prevent additional requests while one is pending? Seems like a  
dangerous proposition in a stateless system where the initial request  
might not return?

The short answer is to not click like that I know… 🙂

However, I am looking for any insight.

thanks,  
Rick