@Hynekcer Its not that I did not want to continue. But there is no nanosecond time left for me right now. The only thing I remember, when I was sniffing in the Fedex response one day. I think I remember that Fedex did not respond with a "time in transit" or similar parameter.
Maybe "time in transit" is only for ground delivery not for aircraft shipments. But its hard to say as there is no Fedex API and parameter description available. I think its a good idea to proceed to the newer Fedex API if they provide better and more detailed information. ionic On Sat, 2011-11-26 at 16:28 -0800, hynekcer wrote: > I fixed international characters for legacy method in collaboration > with user "Ionic Drive" in e-mail communication following the thread > groups.google.com/group/satchmo-users/browse_thread/thread/ > 86ea6bfeeae3955b/ . I did not published the solution becase he found > other bug caused by outdating Fedex code (no "time_in_transit") and he > did not want to continue. > I think the new interface would be better if you have time for it now. > > I would like if no new dependencies would be imported if Fedex is not > used. New packages would be of course included in automatic Quick > Start Installation but it would be possible a manual installation of > unmodified Satchmo without them. It is not as serious as deep > dependencies on livesettings etc. but nobody knows ahead. > Please send a link some day before you commit it to trunk. > > On 26 lis, 23:56, Chris Moffitt <ch...@moffitts.net> wrote: > > 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.
