Great idea, Jeff! Caleb, the UPS site was slammed so apache was timing out before the UPS site could return anything useful. I did a work-around by dropping in the UPS lookup table and resetting the shipping method. On Thu, 2002-12-26 at 14:38, Jeff Dafoe wrote: > > I had this exact problem when the shipping calculation was fscked. For > > example, if you use FedEx Web Lookup and blocked all outgoing > > ports(particularly 80 if I remember correctly) then you would see these > > symptoms as IC chews on itself. > > This issue could be mitigated if someone reworked Business::UPS (UPS.pm) > to use LWP::UserAgent instead of LWP::Simple . You could then set a smaller > timeout value. I would do it if I used UPS. For Business::Fedex its even > easier as that module already uses LWP::UserAgent, you just need to throw a > > $ua->timeout(10); > > right after the > > my $ua = new LWP::UserAgent; > > With a smaller timeout, the web server's connection to UPS or Fedex > should timeout before the web server's connection to the client does. > > Jeff > > _______________________________________________ > interchange-users mailing list > suppressed > http://www.icdevgroup.org/mailman/listinfo/interchange-users -- James P. Kinney III \Changing the mobile computing world/ President and CEO \ one Linux user / Local Net Solutions,LLC \ at a time. / 770-493-8244 \.___________________________./ GPG ID: 829C6CA7 James P. Kinney III (M.S. Physics) <suppressed> Fingerprint = 3C9E 6366 54FC A3FE BA4D 0659 6190 ADC3 829C 6CA7 _______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.