Non-threadsafe libraries and EventMachine about em_aws

[JoshMcKin]

Nice catch. A pull request would be accepted. Hopefully AWS will be updated with a thread safe autoload feature before the current default ruby autoload is depreciated.

Thanks,

[JoshuaOSHickman]

I issued a pull request for the change -- if you are worried about those cowboys without Gemfile.locks, I can submit the change to the README.

[JoshMcKin]

released in 0.1.2

[JoshMcKin]

Not too concerned about folks without Gemfile.locks in their deployed applications, at this time. If it becomes an issue we can address it then.

Thanks,

[johnkchow]

Ah, so this is why I was seeing those weird NoMethodErrors when I tried using the gem + EM months ago. @JoshMcKin just want to let you know that since the update, I haven't seen the NoMethodError pop up in my apps. Thanks guys.

[JoshuaOSHickman]

Yeah, this is a weird one, no doubt. Another thing I noticed is that the SessionSigner is often auto-loaded incorrectly by amazon. I believe the registered autoloads are conflicting depending on the order of loading the libraries -- putting the correct order in the readme/ making this gem more flexible would be nice for people.

Symptom is having NoMethodError on SessionSigner, which has only the method defined here.

@JoshMcKin you seen anything like this?

[JoshMcKin]

Nope. I run async Rails 3.0 and never saw this issue.