Could the flag be a user-defined property of the anchor itself, such as [element].busy = [bool]? Your updateContent function could then check this.busy before starting another request/transition, and each link on the page would cap its requests independently. You could even prototype anchors to have a busy property of false by default to avoid undefined errors when groping for the property.
The only problem I've noticed is that sometimes when trying to grab an anchor by id to access its properties I get the url string of the anchor instead of the element itself, as if anchors are "special" in some way (ffox). I don't expect that issue in this implementation though. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
