Thank you! That makes me feel less guilty about going head-to-head with Chris/stalepez in a "you are too ignoring me and my needs" whinefest.
I suspect Tim had the correction queued up -- I mean, he made it within 10 minutes of my guess as to what was causing the problem, and they would need some transparently accessible code to make a change that quickly. (They do seem to make all their changes directly to the production environment, which freaks me out.) I'm glad I researched the issue, though, because I had assumed LT's coding was 100% at fault (adding to my disdain), and really Amazon shares the responsibility for not standardizing their XML output. It's a disservice to all developers using Amazon's web services.
no subject
Date: 2006-10-29 08:00 am (UTC)I suspect Tim had the correction queued up -- I mean, he made it within 10 minutes of my guess as to what was causing the problem, and they would need some transparently accessible code to make a change that quickly. (They do seem to make all their changes directly to the production environment, which freaks me out.) I'm glad I researched the issue, though, because I had assumed LT's coding was 100% at fault (adding to my disdain), and really Amazon shares the responsibility for not standardizing their XML output. It's a disservice to all developers using Amazon's web services.