Fixes #263 (Rename eventloops)
Make sure to release content buffer

When using HttpObjectAggregationConfigurator I
was getting a leak error if the response from
the server was empty:

```
Nov 02, 2014 6:01:41 PM io.netty.util.ResourceLeakDetector reportLeak
SEVERE: LEAK: ByteBuf.release() was not called before it's garbage-collected.
```

The difference seems to be the type of ByteBuf
for the content. HttpObjectAggregationConfigurator
will cause the type to be CompositeByteBuf
instead of EmptyByteBuf and when the response
is empty is isn't readable, but still needs to
be cleaned up.
Fixes #205 #209 #220 #222

#205 (Move SSE related classes to http): This is a new implementation of SSE for some optimizations and spec compliance.
#209 (Deprecated all SSE classes in text pkg): SSE is only applicable to HTTP.
#220 (SSE Output confusion): Default case only emits data event.
#222 (Improved SSE API): Better construction semantics.
#30 (Optimized SSE decoder): Rewrite of the existing decoder.
Fixed a memory leak in SSEDecoder
Merge pull request #265 from brharrington/bytebuf-leak

Make sure to release content buffer
Merge pull request #266 from NiteshKant/0.x

New SSE implementation
Merge branch '0.x' of https://github.com/ReactiveX/RxNetty into 0.x
Updated CHANGES.md for 0.3.17
Merge pull request #268 from NiteshKant/0.x

Fixed a memory leak in SSEDecoder
bumping the version manually
Merge pull request #1 from ReactiveX/0.x

update from origin