Re: UPS Package

Clay Loveless wrote: >On 12/2/04 12:33 PM Pacific Time, Joe Stump (joe@joestump.net) wrote: > >> I will say this about UPS's interface: >> >> 1.) It's INSANELY complex (ie. you can put 8 boxes in 12 different zips >> in a single request) >> 2.) It's slow. >> >> I'd be up for PEAR-ifying my UPS code. So we might have both a UPS and >> FedEx driver. It would be nice to be able to do cost lookups too (ie. >> an 8lb box to 98122 will cost $10.32). >> >> --Joe > >The same is true of the FedEx API -- incredibly complex, 200+ page manual >for options including hazardous shipments, "hold at FedEx location" options, >multi-package shipments with parent and sub tracking numbers, etc. > >Seems like it would make sense for each driver to support some basics in an >initial release, and then expand into the carrier-specific features in >subsequent releases, just to keep the overall complexity manageable. I have called Chronopost. The person I talked to in the end was very nice and promised to send me some documentation about their web services sometime next week. The service is apparently using SOAP and allow for rates, shipping and labels queries and maybe more. Unfortunately, they don't have a complete documentation yet. Once I get more info, we will be able to compare the proposed interfaces and see if a common API is reasonable. Package Services_Shipping looks like a good name. Bertrand Mansion Mamasam