Existing users, 
 SafariNoTimeout - 1.1haxie changes 60 second connection timeout in Safari (not necessary as of OS X 10.3.6) |
|
||||||||||||||
|
|||||||||||||||
Feedback Summary:
| This Version: | |||||
| Overall Rating: | Not rated (0.0) | Features: | Not rated (0.0) | Support: | Not rated (0.0) |
| Ease of Use: | Not rated (0.0) | Quality / Stability: | Not rated (0.0) | Price: | Not rated (0.0) |
Key to Types of Feedback:
Reviews 
Troubleshooting 
Usage Tips 
Developer Notes 
Commentary 
Featured Reviews
All Feedback: 1 - 10 of 10
not so sure any more - Version: 1.0, 1/28/2004 05:28PM PST
(2 of 3 users found this comment useful)
plaintiger
Didnt' work for me 
- Version: 1.0, 12/9/2003 01:38PM PST
(5 of 7 users found this comment useful)
Luhmann
Nice idea, and I like other stuff by these developers, but this didn't work for me. It didn't improve Safari performance with timeouts, and it sucked up processor/CPU power. I had to remove it. (I have an iBook with 10.3.1).
most excellent - Version: 1.0, 11/22/2003 05:40PM PST
(0 of 4 users found this comment useful)
plaintiger
still more kudos to the great Unsanity! :)
I LOVE UNSANITY!!! - Version: 1.0, 5/14/2003 03:52PM PST
(0 of 8 users found this comment useful)
Mayhem!
'nuff said. :)
Most Recent Replies: View All 1 Replies
- I LOVE UNSANITY!!!
Great - Version: 1.0, 5/5/2003 10:18PM PST
(5 of 7 users found this comment useful)
morserjdotmac
helps those of us working in large databases.
Lovely solution to… - Version: 1.0, 4/17/2003 08:51PM PST
nnager
a frustrating problem. Thank you very, very much Unsanity!
Sweet! This addresses… - Version: 1.0, 4/17/2003 06:05AM PST
Xapplimatic
my biggest problem with Safari (aside from the can't load Google.com on my PowerBook issue)..
i've been having a problem in Safari 1.1.1 for some time wherein a page doesn't load for some reason, and then i either tell it to stop and try to go to a different site, or i let it keep chugging while i try to go to a different site in a new tab or whatever, but i find i now can't get to any site; basically, my connection's broken (although i have cable) and i can't get anyplace in Safari until i quit it and relaunch, at which point it works fine until the next time it happens (and it always happens eventually). i would think this a function of Safari's memory leak or something, but for the fact that i don't have this problem on the copy of Safari i have running on my other machine...
oh wait...the other machine *does* have SafariNoTimeout on it. hmm.
but the other machine's copy of Safari is also 1.0.1 (that machine can't run Panther). would that have anything to do with it? and would SafariNoTimeout?
jeez, i'm confused.
:)