Yes, it would indeed be useful. There are plans for some ajax refactoring in 1.6.1. Most of these annoyances will most likely be fixed.
-- kangax On Jun 27, 12:24 pm, Dan Delaney <[EMAIL PROTECTED]> wrote: > On Jun 26, 8:06 pm, kangax <[EMAIL PROTECTED]> wrote: > > > You might want to take a look at: > >http://dev.rubyonrails.org/ticket/10191 > >http://dev.rubyonrails.org/ticket/10030 > >http://dev.rubyonrails.org/ticket/3730 > > Thanks Kangax. Those first two don't have anything to do with a > Timeout function, but the last one is a patch that does EXACTLY what I > described in the OP! > > Unfortunately, the patch was submitted two YEARS ago, didn't work in > Safari, and so was never included in prototype. Maybe I'll download > the patch and see if I can get it working in Safari. Or maybe Matt > would like to take a look at it. He seems awfully motivated :-) Thanks > for that monkey patch, Matt. > > I can't express enough how incredibly useful it would be to be able to > set a separate timeout period and function for each Ajax.Request. > > --Dan --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
