* Corrected boost version number for introduction of shutdown_service() (it was introduced as a private pure virtual method to boost::asio::io_service::service in version 1.47.  io_service::service is used as a base class for cgi/fcgi services...)
* Corrected boost version number for change from system_category (data) to system_category() method, which was a breaking change introduced in boost version 1.44
* Corrected <= to >= for shutdown_service() and system_category().
* Added boost version check for references to system_category to system_category() for win32_acceptor_service_impl.hpp and request_acceptor_service.hpp.
The binary 'and' bitwise operator being auto-evaluated as bool was not having the behavior the authors expected for parse_cookies and parse_form_only because these enumerations are not single bit values (i.e. 1,2,4,8,16) but a combination of single bit values.  As a result values were evaluating to true for the expression when not expected, resulting in exception behavior.  This has been fixed by explicitly comparing against the specified values after the bitwise 'and'.
* This is a work-around for a completely broken implementation. Specifically, thefunction call stack looks like:

    fcgi_request_service<Protocol>::handle_begin_request_header ->
    fcgi_request_service<Protocol>::parse_post_vars ->
    request_base::parse_post_vars ->
    form_parser::parse

Form parser explicitly states in documentation that valid form encodings are application/x-www-form-urlencoded, and multipart/form-data.  I am not familiar enough with HTML forms to know if this restriction is legitamite for html forms or not.  However, it is an invalid restriction for HTML POST in general, as long as the mime type is at least IANA registered (http://www.iana.org/assignments/media-types).

The code change is to allow POST of any (presumably IANA registered) mime type.  If the specific service implementation doesn't want to except it, then it can always return an error, but the library aught not prevent the server from accepting valid mime types, even if the server implementation hast to parse it manually.

(This problem was discovered when attempting to implement a RESTful service which accepts GET/POST for application/json)
* Fixed a couple of Windows API calls where warning was generated for size_t being passed to DWORD argument generated warnings on x64 build.
* Fixed a few cascading size_t to int conversion warnings on x64 build.
* Fixing bug in clear(), as the request is going to be reused, and the id needs to be cleared so that it will not apply multiplexing logic on the following request.  (Some servers increase the id count, such as IIS)  The library was always giving an error "Multiplexing connections are not yet fully supported." on every second request, even though there wasn't actually any multiplexing going on.
Merge branch 'master' of https://github.com/benmccart/cgi
* Completely refactored win32_acceptor_service_impl.hpp and related dependencies to handle either TCP or PIPE transport (FastCGI specification specifically says the host server may use either one, and a FastCGI application needs to detect which one is being used.)
* Fixed basic_request_acceptor.hpp to work with boost::asio tcp connections since it was incorrectly implemented for a FastCGI application.  The web server has already created a socket and is listening for a new connection.  (Reading the FastCGI specification will give the reader an incorrect interpretation of section 3.2 if section 2.2 is not taken into consideration.)
* Refactored to handle admin requests (i.e. GET_VALUES)
* Removed some depricated (unused) code.
* Attempted to get asynchronous accepts working -- failed!  Entire portions of the library will have to be rewritten to accomplish this.
* Got synchronous accepts to be non-blocking when waiting for the next message (to facilitate shutting down when receiving SIGTERM.
* Now using boost asio local::stream::socket / ip::tcp::socket / windows::stream_handle direclty (and exclusively) to handle the fcgi connection (which could be tcp socket or a 'pipe').  This makes the win32_accept_service_impl.hpp pretty close to a cross-platform implementation.
* Fixed ugly bug in client.close() that was writing fcgi END packet when there was no request in progress!
* Renaming the connection file since it is not a windows implementation but a fcgi cross-platform connection  (minus connect, which can be migrated here later.)
* Changing pipe implementation back to internal implementation of anonymouse_pipe (named pipe really) due to boost::asio::windows::stream_handel requiring FILE_FLAG_OVERLAPPED, which some web servers do not supply (mod_fcgid on Apache).
* Implementing lame work-around (i.e. worker thread) so that async read/write will at least sort/of work with anonymous_pipe.  This is necessary due to ReadFileEx/WriteFileEx requiring FILE_FLAG_OVERLAPPED.  (FILE_FLAG_OVERLAPPED can't be added with ReOpenFile() due to pending IO at start-up.)
Reworked TCP acceptor code to get it to match wording of FastCGI specification...   still a work in progress but it is closer.
Merge pull request #6 from benmccart/master

Three changes to fixes compilation/bugs