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. Indeed, let's start with the basics :) Would it be possible that you both post your code somewhere along with related documents (API documentation for the different services for example) ? This way, we could see if there are similarities and define the kind of problems that need to be solved first. Then we could define a common driver-based API and start to implement. I will take care of the Chronopost driver if I can manage to find some information and get in touch with someone there. Bertrand Mansion Mamasam