I recently had the need to go in and make some custom changes to Fedex. In the process, I learned that Satchmo's current XML implementation is a bit old and needs to be updated. The current version works with the legacy Fedex servers but won't migrate cleanly to the newer and more up to date ones.
After fiddling around with it for a while, I think we have two options going forward. 1. Modify the existing XML version to use the newer syntax and keep it mostly the same as the current implementation. 2. Migrate to a newer API version using SOAP. It looks like there have been a few folks that have done this so I think the implementation effort is fairly limited but it would introduce new dependencies for the Fedex module, namely suds and python-fedex - http://code.google.com/p/python-fedex/ Under the hood there aren't that many differences between SOAP and the XML api but after trying to read the Fedex docs for a while, they are really pushing towards the SOAP approach. Having some work already in place for the Python-fedex module, I think it's good to leverage instead of recreating our own. As you can tell, I'm leaning towards jumping to option #2 but wanted some feedback from the group. Also, some folks have already started working on this integration so I'd appreciate any updates or code contribution to make this easier. Interested in the group's input. -Chris -- You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to satchmo-users@googlegroups.com. To unsubscribe from this group, send email to satchmo-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en.
