Restler 3.0.0 Release Candidate 1
Fixes #71 iAuthenticate in Restler 3 RC1
Fatal error: Can't inherit abstract function Luracast\Restler\iFilter::__isAllowed() (previously declared abstract in Luracast\Restler\iAuthenticate)
Restler 3 Release Candidate 2
Restler 3 Release Candidate 3
Added two more ways to exclude API's from explorer/documentation
 - `Resources::$excludedHttpMethods` (array)
 - `Resources::$excludedPaths` (array)
minor corrections in comments
Fixes Resources not to include namespace when the return type is array of custom class
Fixes a bug with ValidationInfo parsing @choice inline comment
Improves inline comment parsing by array conversion when delimiter is found and tag is not @pattern
Fixes a php notice when body parameters are used with out `request_body`
Fixes fatal error when the JSON sent in the request body is not an object or array
Fixes a bug in XmlFormat parsing XML content to array
Added Defaults::$cacheDirectory to set cache directory in one central place
In Restler class,
 - removed unused baseDir property
 - changed baseUrl as a protected property which can be accessed externally as _baseUrl (read only)
 - setting Defaults::$cacheDirectory to the cache folder under the same folder where index.php (gateway) resides

Resources class updated to use _baseUrl to work with the changes above
HumanReadableCache now checks if the cache directory is writeable on construct when in production mode and throws exception which can be made visible to the user. Fixes #90
- fixes #93 unicode unescaping bug in JsonFormat for PHP < 5.4
 - fixes the order so that responseFormat->setCharset is called before decoding
Fixes resources bug in which apis that are named to be a substring of another api list that other api as part of them

Example:- if we have 2 API called author and authors, author will include the apis that has to be listed only under authors
Fix for #84 Accept-Language priorities to choose the best match
Adding JSONP support with `JsFormat` closes #78.  JSONP can optionally include headers metadata as part of the resulting data for convenience
Fixes #96 "Forbidden: Content type is not supported" error on nginx servers when the client is not sending content type header