Closed GoogleCodeExporter closed 8 years ago
Since it predates them and it's not broken, why?
Original comment by ingen...@gmail.com
on 20 Mar 2012 at 3:23
Let the experts do the special things then others need not to care about the
details.
Maybe we can gain better performance.
Original comment by matrix3...@gmail.com
on 20 Mar 2012 at 3:33
While I agree with you and I like both grizzly and netty (have used both!), I
think it's also possible that inserting an abstraction layer in there could
make it hard to do some of the things we currently do or could actually get in
the way of performance. It also adds a dependency outside the JDK.
Both are possibly true. If you'd like to prove out the concept that'd be
great. At the moment, it doesn't seem to make sense to replace it because
there's a possible better implementation.
It'd be really just a reimplementation of the MemcachedNode class if you want
to prove out any advantage.
Original comment by ingen...@gmail.com
on 20 Mar 2012 at 4:48
I will try that out.
Original comment by matrix3...@gmail.com
on 20 Mar 2012 at 6:19
Original issue reported on code.google.com by
matrix3...@gmail.com
on 20 Mar 2012 at 2:16