I have been successfully using the latest mongrel and upload progress plugin with safari but firefox seems to have some issues with any request that takes longer than 5 seconds to complete. You get the "Warning: Unresponsive Script" screen. Apparently this problem is fixable by following this: http://computer-vet.com/weblog/2006/04/28/ firefox_warning_unresponsive_script.html Telling my users to go there and do that is not something that I''m willing to do, so I''m wondering if anyone out there knows how to change this on the fly or if there''s some other trick to make firefox behave during a file upload? Or are others not seeing this problem at all? -Michael http://javathehutt.blogspot.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060919/53c8b498/attachment.html
I''m not seeing this problem at all. I''m using mongrel 0.3.13.3 and mongrel_upload_progress 0.1. Firefox 1.5.0.7. I''m not using the helpers, however -- I''m using some heavily-hacked code on the client side because of some special requirements. Contact me off-list to discuss the code -- it''s not available for public consumption (yet, hopefully.) I don''t see why you should have a long-running script anyway. The form should post to an iframe and then set up a PeriodicalExecuter (which in turn uses setInterval). If I''m not mistaken, that function should return immediately. As long as you''re using asynchronous requests for the updates, you shouldn''t block. But I have been known to be wrong before, and I could be wrong now. ;-) --be On Sep 19, 2006, at 8:51 PM, Michael Kovacs wrote:> I have been successfully using the latest mongrel and upload > progress plugin with safari but firefox seems to have some issues > with any request > that takes longer than 5 seconds to complete. You get the "Warning: > Unresponsive Script" screen. Apparently this problem is fixable by > following this: > > http://computer-vet.com/weblog/2006/04/28/ > firefox_warning_unresponsive_script.html > > Telling my users to go there and do that is not something that I''m > willing to do, so I''m wondering if anyone out there knows how to > change this on the > fly or if there''s some other trick to make firefox behave during a > file upload? Or are others not seeing this problem at all? > > -Michael > http://javathehutt.blogspot.com > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060919/b8ef8bdd/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2421 bytes Desc: not available Url : http://rubyforge.org/pipermail/mongrel-users/attachments/20060919/b8ef8bdd/attachment-0001.bin
Well even if I pull all the javascript code and just do a straight form post with no progress I get this behavior in firefox. The upload request is taking more than 5 seconds so firefox is popping up that dialog. IE and safari work fine and for the first time ever it''s firefox that I''m cursing instead of IE or safari. Go figure :-) -Michael http://javathehutt.blogspot.com On Sep 19, 2006, at 8:28 PM, Brad Ediger wrote:> I''m not seeing this problem at all. I''m using mongrel 0.3.13.3 and > mongrel_upload_progress 0.1. Firefox 1.5.0.7. I''m not using the > helpers, however -- I''m using some heavily-hacked code on the > client side because of some special requirements. Contact me off- > list to discuss the code -- it''s not available for public > consumption (yet, hopefully.) > > I don''t see why you should have a long-running script anyway. The > form should post to an iframe and then set up a PeriodicalExecuter > (which in turn uses setInterval). If I''m not mistaken, that > function should return immediately. As long as you''re using > asynchronous requests for the updates, you shouldn''t block. But I > have been known to be wrong before, and I could be wrong now. ;-) > > --be > > On Sep 19, 2006, at 8:51 PM, Michael Kovacs wrote: > >> I have been successfully using the latest mongrel and upload >> progress plugin with safari but firefox seems to have some issues >> with any request >> that takes longer than 5 seconds to complete. You get the >> "Warning: Unresponsive Script" screen. Apparently this problem is >> fixable by following this: >> >> http://computer-vet.com/weblog/2006/04/28/ >> firefox_warning_unresponsive_script.html >> >> Telling my users to go there and do that is not something that I''m >> willing to do, so I''m wondering if anyone out there knows how to >> change this on the >> fly or if there''s some other trick to make firefox behave during a >> file upload? Or are others not seeing this problem at all? >> >> -Michael >> http://javathehutt.blogspot.com >> >> > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060919/79c1a506/attachment.html
Can you post sample code? My Firefox behaves fine with long-running HTTP requests. Perhaps Mongrel is taking too long to respond? On Sep 20, 2006, at 12:35 AM, Michael Kovacs wrote:> Well even if I pull all the javascript code and just do a straight > form post with no progress I get this behavior in firefox. The > upload request is taking more than 5 seconds > so firefox is popping up that dialog. IE and safari work fine and > for the first time ever it''s firefox that I''m cursing instead of IE > or safari. Go figure :-) > > -Michael > http://javathehutt.blogspot.com > > On Sep 19, 2006, at 8:28 PM, Brad Ediger wrote: > >> I''m not seeing this problem at all. I''m using mongrel 0.3.13.3 and >> mongrel_upload_progress 0.1. Firefox 1.5.0.7. I''m not using the >> helpers, however -- I''m using some heavily-hacked code on the >> client side because of some special requirements. Contact me off- >> list to discuss the code -- it''s not available for public >> consumption (yet, hopefully.) >> >> I don''t see why you should have a long-running script anyway. The >> form should post to an iframe and then set up a PeriodicalExecuter >> (which in turn uses setInterval). If I''m not mistaken, that >> function should return immediately. As long as you''re using >> asynchronous requests for the updates, you shouldn''t block. But I >> have been known to be wrong before, and I could be wrong now. ;-) >> >> --be >> >> On Sep 19, 2006, at 8:51 PM, Michael Kovacs wrote: >> >>> I have been successfully using the latest mongrel and upload >>> progress plugin with safari but firefox seems to have some issues >>> with any request >>> that takes longer than 5 seconds to complete. You get the >>> "Warning: Unresponsive Script" screen. Apparently this problem is >>> fixable by following this: >>> >>> http://computer-vet.com/weblog/2006/04/28/ >>> firefox_warning_unresponsive_script.html >>> >>> Telling my users to go there and do that is not something that >>> I''m willing to do, so I''m wondering if anyone out there knows how >>> to change this on the >>> fly or if there''s some other trick to make firefox behave during >>> a file upload? Or are others not seeing this problem at all? >>> >>> -Michael >>> http://javathehutt.blogspot.com >>> >>> >> _______________________________________________ >> Mongrel-users mailing list >> Mongrel-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/mongrel-users > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060920/b33de72d/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2421 bytes Desc: not available Url : http://rubyforge.org/pipermail/mongrel-users/attachments/20060920/b33de72d/attachment-0001.bin
I''m using the sample code that''s on the mongrel documentation page. -Michael http://javathehutt.blogspot.com On Sep 20, 2006, at 7:44 AM, Brad Ediger wrote:> Can you post sample code? My Firefox behaves fine with long-running > HTTP requests. > > Perhaps Mongrel is taking too long to respond? > > On Sep 20, 2006, at 12:35 AM, Michael Kovacs wrote: > >> Well even if I pull all the javascript code and just do a straight >> form post with no progress I get this behavior in firefox. The >> upload request is taking more than 5 seconds >> so firefox is popping up that dialog. IE and safari work fine and >> for the first time ever it''s firefox that I''m cursing instead of >> IE or safari. Go figure :-) >> >> -Michael >> http://javathehutt.blogspot.com >> >> On Sep 19, 2006, at 8:28 PM, Brad Ediger wrote: >> >>> I''m not seeing this problem at all. I''m using mongrel 0.3.13.3 >>> and mongrel_upload_progress 0.1. Firefox 1.5.0.7. I''m not using >>> the helpers, however -- I''m using some heavily-hacked code on the >>> client side because of some special requirements. Contact me off- >>> list to discuss the code -- it''s not available for public >>> consumption (yet, hopefully.) >>> >>> I don''t see why you should have a long-running script anyway. The >>> form should post to an iframe and then set up a >>> PeriodicalExecuter (which in turn uses setInterval). If I''m not >>> mistaken, that function should return immediately. As long as >>> you''re using asynchronous requests for the updates, you shouldn''t >>> block. But I have been known to be wrong before, and I could be >>> wrong now. ;-) >>> >>> --be >>> >>> On Sep 19, 2006, at 8:51 PM, Michael Kovacs wrote: >>> >>>> I have been successfully using the latest mongrel and upload >>>> progress plugin with safari but firefox seems to have some >>>> issues with any request >>>> that takes longer than 5 seconds to complete. You get the >>>> "Warning: Unresponsive Script" screen. Apparently this problem >>>> is fixable by following this: >>>> >>>> http://computer-vet.com/weblog/2006/04/28/ >>>> firefox_warning_unresponsive_script.html >>>> >>>> Telling my users to go there and do that is not something that >>>> I''m willing to do, so I''m wondering if anyone out there knows >>>> how to change this on the >>>> fly or if there''s some other trick to make firefox behave during >>>> a file upload? Or are others not seeing this problem at all? >>>> >>>> -Michael >>>> http://javathehutt.blogspot.com >>>> >>>> >>> _______________________________________________ >>> Mongrel-users mailing list >>> Mongrel-users at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/mongrel-users >> >> _______________________________________________ >> Mongrel-users mailing list >> Mongrel-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/mongrel-users > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060920/08521452/attachment.html
Well, a quick Google search seems to indicate that this is a widespread problem with uploads and FF/1.5. (Enough so that some sites list this issue in their FAQs). It seems to happen under one of two circumstances: 1) Script takes too long to execute 2) Server takes too long to respond or is not available. Barring #2, I would see if there are other scripts running concurrently that might be blocked by a long file upload. I would imagine that if you had a number of JS-intensive extensions installed (View Formatted Source, Web Developer, Adblock, etc.), they might be causing this error. Just a guess, though... I''m out of my league now. I have my dom.max_script_run_time set to 10 and I only very rarely get this warning while a script is still running (i.e., not locked up.) --be On Sep 20, 2006, at 11:59 AM, Michael Kovacs wrote:> I''m using the sample code that''s on the mongrel documentation page. > > -Michael > http://javathehutt.blogspot.com > > On Sep 20, 2006, at 7:44 AM, Brad Ediger wrote: > >> Can you post sample code? My Firefox behaves fine with long- >> running HTTP requests. >> >> Perhaps Mongrel is taking too long to respond? >> >> On Sep 20, 2006, at 12:35 AM, Michael Kovacs wrote: >> >>> Well even if I pull all the javascript code and just do a >>> straight form post with no progress I get this behavior in >>> firefox. The upload request is taking more than 5 seconds >>> so firefox is popping up that dialog. IE and safari work fine and >>> for the first time ever it''s firefox that I''m cursing instead of >>> IE or safari. Go figure :-) >>> >>> -Michael >>> http://javathehutt.blogspot.com >>> >>> On Sep 19, 2006, at 8:28 PM, Brad Ediger wrote: >>> >>>> I''m not seeing this problem at all. I''m using mongrel 0.3.13.3 >>>> and mongrel_upload_progress 0.1. Firefox 1.5.0.7. I''m not using >>>> the helpers, however -- I''m using some heavily-hacked code on >>>> the client side because of some special requirements. Contact me >>>> off-list to discuss the code -- it''s not available for public >>>> consumption (yet, hopefully.) >>>> >>>> I don''t see why you should have a long-running script anyway. >>>> The form should post to an iframe and then set up a >>>> PeriodicalExecuter (which in turn uses setInterval). If I''m not >>>> mistaken, that function should return immediately. As long as >>>> you''re using asynchronous requests for the updates, you >>>> shouldn''t block. But I have been known to be wrong before, and I >>>> could be wrong now. ;-) >>>> >>>> --be >>>> >>>> On Sep 19, 2006, at 8:51 PM, Michael Kovacs wrote: >>>> >>>>> I have been successfully using the latest mongrel and upload >>>>> progress plugin with safari but firefox seems to have some >>>>> issues with any request >>>>> that takes longer than 5 seconds to complete. You get the >>>>> "Warning: Unresponsive Script" screen. Apparently this problem >>>>> is fixable by following this: >>>>> >>>>> http://computer-vet.com/weblog/2006/04/28/ >>>>> firefox_warning_unresponsive_script.html >>>>> >>>>> Telling my users to go there and do that is not something that >>>>> I''m willing to do, so I''m wondering if anyone out there knows >>>>> how to change this on the >>>>> fly or if there''s some other trick to make firefox behave >>>>> during a file upload? Or are others not seeing this problem at >>>>> all? >>>>> >>>>> -Michael >>>>> http://javathehutt.blogspot.com >>>>> >>>>> >>>> _______________________________________________ >>>> Mongrel-users mailing list >>>> Mongrel-users at rubyforge.org >>>> http://rubyforge.org/mailman/listinfo/mongrel-users >>> >>> _______________________________________________ >>> Mongrel-users mailing list >>> Mongrel-users at rubyforge.org >>> http://rubyforge.org/mailman/listinfo/mongrel-users >> >> _______________________________________________ >> Mongrel-users mailing list >> Mongrel-users at rubyforge.org >> http://rubyforge.org/mailman/listinfo/mongrel-users > > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users-------------- next part -------------- An HTML attachment was scrubbed... URL: http://rubyforge.org/pipermail/mongrel-users/attachments/20060920/238e7354/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 2421 bytes Desc: not available Url : http://rubyforge.org/pipermail/mongrel-users/attachments/20060920/238e7354/attachment-0001.bin
Possibly Parallel Threads
- mongrel_upload_progress question/possible suggestion
- Does Ajax.PeriodicalUpdater have a shield against multiple parallel executions?
- PeriodicalExecuter stops when form is submitted in Safari 3
- Does prototype get rid of PeriodicalExecuter once it is stop()?
- how to use upload progress?