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 would like to see Services_Shipping, and then subpackages Services_Shipping_UPS, Services_Shipping_Fedex. Each should have their own release cycle. Either that or each should have the same API and just be separate. After all do we really need a class to do: <?php $a = Services_Shipping('ups'); ?> when we can just do: <?php $a = new Services_Shipping_UPS; ?> Now, if Services_Shipping contains methods for aggregating data (for instance, a cost comparison from many shippers), then it would be useful. In addition, you can use the new package.xml format as soon as I finish PEAR 1.4.0 to set up default installs and other perks. Greg