Update dependency versions for release
[maven-release-plugin] prepare release nifty-parent-0.10.0
[maven-release-plugin] prepare for next development iteration
commit 413e7c23f846a972cd8d4e8fb8313a9876546488
Author: Henning Schmiedehausen <henning@schmiedehausen.org>
Date:   Wed Nov 20 14:20:35 2013 -0800

    Split read based timeouts.

    A Nifty client actually has to deal with two separate timeouts:

    - receive timeout - the maximum amount of time that the caller is willing to wait
      for an I/O request to complete
    - read timeout - the maximum amount of time that the client is willing for the
      server to make any progress

    These times can be very different. e.g. a server might trickle a request sending a
    packet every three seconds for a long time and the caller is willing to wait minutes
    for a request to complete as long as it makes progress.

    This patch fixes the name confusion around read, request and receive timeouts in the
    nifty client code, uses consistent naming everywhere and adds a new timeout (receiveTimeout).

    Existing code should still work fine as both timeouts are set to the same value by default.
Update pom to build with maven 3.1.1

- latest base pom
- shade plugin 2.1
[maven-release-plugin] prepare release nifty-parent-0.11.0
[maven-release-plugin] prepare for next development iteration
Add pluggable security (authentication and encryption)

Also add a no-op security factory which is also the default. Other
factories (user-written) can be plugged in to use SSL, SASL, Kerberos,
or other types of authentication and encryption.
make accept backlog tunable
Use guava 16.0.1 to match swift
Add missing import to fix build
Upgrade to latest facebook-oss-pom snapshot