5 Replies Latest reply on Nov 23, 2009 7:46 PM by Aaron Walker

    Netty buffer classes

    Tim Fox Master

      Currently we use a forked copy of some older Netty buffer classes when we need to use buffers internally but don't want a runtime netty dependency.

      There are some problems with this approach:

      1) This buffers get quickly out of date and don't have any new performance enhancements/bug fixes done to the versions in netty

      2) When copying to/from real netty buffers this involves extra copying.

      I'm proposing we remove these forked classes and just use the real netty buffers.

      The down side of this means that core will have a runtime depency on the netty jar.

      wdyt?