This is designed to make it easy to build API authentication without re-inventing the crypto/schema wheel. It should enable a common set of client libraries to be built. Includes: * complete documentation of: - the schema - the reference implementation - how to create and deploy a custom implementation * unit tests against the Amazon API documentation
…th the previously suggested solution
…d web media formats tiff, mpeg, etc. Without it Firefox does not know what to do with an extensionless tiff.
…derspecs wants to make a bunch of mochiutf8 less clear.
There are a number of examples in otp of libraries that have .app files w/o a mod section. So it appears that it is perfectly valid to not keep around a bunch of erlang/otp application infrastructure that is never used. There is also as has been pointed out many times no good reason to ever call application:start(mochiweb) and the current incarnation of mochiweb:start() didn't do anything correctly anyway because we have a dependence on the inets application which we don't start. The most reasonable thing to do seems like to remove this infrastructure and only care about the .app file as it's needed by rebar and other tools like dialyzer.