Speed up the multipart parser
Fix indentation
Added multipart parsing benchmark
Use the new binary module to make multipart parsing 3x faster than with the previously suggested solution
Tell about dependency change in README
run once in test
convert tabs to spaces
remove .swp file and add to .gitignore
Merge branch 'faster_multipart_parsing'
Add mochiweb_request:accepted_content_types/1

%% @spec accepted_content_types([string() | binary()]) -> [string()] | bad_accept_header
%%
%% @doc Filters which of the given media types this request accepts. This filtering
%%      is performed by analyzing the "Accept" header. The returned list is sorted
%%      according to the preferences specified in the "Accept" header (higher Q values
%%      first). If two or more types have the same preference (Q value), they're order
%%      in the returned list is the same as they're order in the input list.
%%
%%      Examples
%%
%%      1) For a missing "Accept" header:
%%         accepted_content_types(["text/html", "application/json"]) ->
%%             ["text/html", "application/json"]
%%
%%      2) For an "Accept" header with value "text/html, application/*":
%%         accepted_content_types(["application/json", "text/html"]) ->
%%             ["application/json", "text/html"]
%%
%%      3) For an "Accept" header with value "text/html, */*; q=0.0":
%%         accepted_content_types(["text/html", "application/json"]) ->
%%             ["text/html"]
%%
%%      4) For an "Accept" header with value "text/html; q=0.5, */*; q=0.1":
%%         accepts_content_types(["application/json", "text/html"]) ->
%%             ["text/html", "application/json"]
%%
Removed one mochiweb_request:accepts_content_type/1 function clause

This was not a necessary clause because the regexp replace operation
accepts iolists.
Add one more test for mochiweb_request:accepted_content_types/1
An example of an Amazon Web Services style HMAC api for mochiweb.

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
tweak to doco
Fix up of README

Proper spell-checking and re-read for sense. A couple of minor additions but mostly spelling/grammer
Fixed up the code

Removed the misformed define (and reported it to erlang-bugs as it shouldn't have ever compiled)
Rewritten the headers stuff
Removed export all
Merge remote branch 'hypernumbers/master' into hmac-example-53
erlang-mode comments and indentation
Merge branch 'hmac-example-53'
Merge pull request #50 from fdmanana/remove_function_clause

Removed one mochiweb_request:accepts_content_type/1 function clause