[ANN] Project Grizzly 1.7.2 released

> 1.7.2 February 21 [Beta]
> -----------------------
> + Fix for https://glassfish.dev.java.net/issues/show_bug.cgi?id=4161 [http]
> + Fix https://grizzly.dev.java.net/issues/show_bug.cgi?id=57 [grizzly]
> + Fix https://grizzly.dev.java.net/issues/show_bug.cgi?id=64 [grizzly]
> + Added Peregrine code base. [contribs]
> + Fix for https://grizzly.dev.java.net/issues/show_bug.cgi?id=63 [grizzly]
> + Fix for Issue https://grizzly.dev.java.net/issues/show_bug.cgi?id=59 [grizzly]
> + Fix for Issue https://grizzly.dev.java.net/issues/show_bug.cgi?id=51 [grizzly]
> + Fix for Issue https://grizzly.dev.java.net/issues/show_bug.cgi?id=62 [grizzly]
> + The issue was that if I had the application deployed on the root context the static files were working correctly, but the dynamic requests - control
> ler/action were not working correctly. This had to do with the "ActionController::<Abstract/Cgi>Request." settings that were defined in the dispatch.r
> b.  These settings are only required if the application is not at the root context. [jruby]
> + Make GrizzletRequest/Response use the newly added GrizzlyRequest/Response and gives full power to the Grizzly when manipulating the request/response
> , by being able to use InputStream/OutputStream/Reader/Writer, manipulating cookies, uri converter etc. The scope of some set/get aren't proper, but t
> his is an improvement since the previous version of Grizzlet. [comet]
> + Fix for Issue https://grizzly.dev.java.net/issues/show_bug.cgi?id=58 [http]
> + Fix for issue https://grizzly.dev.java.net/issues/show_bug.cgi?id=55 [grizzly]
> + Port fixes from Grizzly 1.0.19.
> + Fix for issue https://glassfish.dev.java.net/issues/show_bug.cgi?id=3975 [jruby]
> + Check for a callbackHandler and if one isn't installed it creates one (identical to the one created if controller == null). This makes TCPConnectorH
> andler a bit easier to use for the the most common case.  [grizzly]
> + Fix the publish response is not sent correctly.  In particular, there is no successful field and is an extra data field.  Need to move the data fiel
> d to a deliver response message. [cometd]
> + Fix the scenario when a cometd.subscribe is transmitted by the client, without a cometd.publish operation (BayeuxCometHandler.subscribe) Add missing
>  annotations. [cometd]