NOTE: I had just realized that the problem I incurred was taking place via SQS (though the same would have been true for parsing the response XML from an S3 operation) -- Not sure why it didn't occur to me to enable SQS on the testing account I set-up for this, but I've now changed that.
The same access keys will work, and if you would like to play with the usage of an x509 certificate for signing requests, let me know and I will get that taken care of.
For quick access,
SQS entry page: http://www.amazon.com/gp/browse.html?node=13584001
SQS code samples and technical documentation: http://developer.amazonwebservices.com/connect/kbcategory.jspa?categoryID=8
Thanks Seo! As with everything you do, there are TONS of people who have and who will be benefiting from your efforts, and this effort in particular is something that will enable some pretty amazing things, so for what its worth, again: Thank you! :)
On 10/21/06, Sanghyeon Seo <[EMAIL PROTECTED]> wrote:
2006/10/22, M. David Peterson <[EMAIL PROTECTED]>:
> I've been out for most of the week, and haven't had much of a chance to come
> back to this, but I did run into an issue with the usage of the expat
> xml.sax parser (unknown 'intern' keyword. I can provide extended error
> information if necessary) when attempting to parse the response XML from
> AWS.
>
> Is this something you encountered and were able to work around (via your
> pyexpat module possibly?)
I am working on it. Commit:
http://svn.sourceforge.net/viewvc/fepy?view=rev&revision=224
--
Seo Sanghyeon
_______________________________________________
users mailing list
[email protected]
http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
--
/M:D
M. David Peterson
http://mdavid.name | http://www.oreillynet.com/pub/au/2354
_______________________________________________ users mailing list [email protected] http://lists.ironpython.com/listinfo.cgi/users-ironpython.com
