 | | Re: jump.cgi
|
| (...) I see no problem either at home or at work. At home, I've got SDSL at 768, and at work there's an amazingly fast connection (think it's currently dual 45Mbit to the general internet). This is with either Mozilla (nightly) or Netscape 4.7x (...) (26 years ago, 14-Aug-00, to lugnet.admin.general)
| | | | | Re: jump.cgi
|
| (...) back (...) Just tried it here at work. Our largest single pipe to the commodity internet is a DS-3 through Qwest and that's the link I'm tracing from me to you (actually it drops into Sprint to get to Pair). Same delay time - up to 4 seconds. (...) (26 years ago, 14-Aug-00, to lugnet.admin.general)
| | | | | Re: jump.cgi
|
| (...) back (...) I have a 768 DSL connection, and I also get a 4 to 5 second delay. I've seen this a lot recently as well, but haven't mentioned it because I wanted to see what types of links do this. (...) On my computer (with IE 5.5) most of the (...) (26 years ago, 14-Aug-00, to lugnet.admin.general)
| | | | | Re: jump.cgi
|
| (...) That is soooo weird. The jump.cgi script runs inside of 1/100 second. On ISDN, you really shouldn't notice more than 1/10 extra added time. Anyone else seeing this strange behavior? BTW, what text shows in your browser's status window while (...) (26 years ago, 14-Aug-00, to lugnet.admin.general)
| | | | | Re: jump.cgi
|
| (...) 128k ISDN. I've tried loading the same page a few times - one with just a single 1.3k image on it and there is a noticable delay between hitting the link then being forwarded to the target URL. The image itself is in my cache and should be (...) (26 years ago, 14-Aug-00, to lugnet.admin.general)
|
|
