Hi,
I am new to both Grizzly and Mina. I just wanted to put out my first
impressions in the hopes that it will help you improve the project.
I read about Grizzly here:
https://grizzly.dev.java.net/presentations/FISL-2007.pdf
I read about Mina here:
http://people.apache.org/~proyal/MINA%20AC%20EU%202007.pdf
1) I find the Mina presentation to be of much higher quality. It was much
easier to understand and got directly to the point.
2) I found the class names in Mina much easier to understand. Consider
IoSession, IoProcessor, IoFilter, IoHandler (for Mina) versus ProtocolChain,
SelectorHandler, SelectionKeyHandler, InstanceHandler (for Grizzly).
In all honestly, when I approach a new API I don't care whether it uses
Selector under the hood or not. You should be using layman terminology that
is easy to understand like Mina does. I can guess what Mina classes do
without reading their documentation purely by their names whereas in order
to understand Grizzly I'd have to both read your documentation as well as
understand NIO terminology. Please, keep your target audience in mind and
use simpler names :)
So in summary I am suggesting you do two things:
1) Write up comprehensive ***easy-to-read*** documentation for Grizzly. What
currently exists on the website is not enough.
2) Simplify the API terminology as much as possible.
If I am given a choice between Mina and Grizzly and I know that Grizzly
might be 30% faster than Mina I am still more likely to use Mina because it
is easier to get started with and it's probably "good enough" for my
use-case. Just my 2 cents :)
Gili
--
View this message in context: http://www.nabble.com/%28Constructive-%29-criticism-of-Grizzly-tf4041631.html#a11481655
Sent from the Grizzly - Users mailing list archive at Nabble.com.