users@grizzly.java.net

Re: NIO client support of Grizzly

From: Wang Yu <Wang.Yu_at_Sun.COM>
Date: Thu, 24 Sep 2009 09:36:58 +0800

Thanks all the replies, this is a really active community:-)

I think the biggest problem is the lack of completed documents and
reference manuals.
When writing something more complex than shown in the tutorials, you
should go to the
source code.

When I went to MINA (http://mina.apache.org), I found something
similar, a simple startup-guide,
some simple tutorials and demos. Maybe that's the way of using open
source frameworks:-)

Best Regards
Wang Yu

 



Alexei Dets wrote:
> Hi!
> Jeanfrancois Arcand wrote:
>
>> Right. In 2.0 we collected a lot of feedback from the community and made
>> major improvement to the framework. Still I *totally* disagree with
>> Alexei saying 1.9.x cannot/should not be used.
>>
>
> Hey, I never told it can't be used, in fact I told otherwise! It can be
> used, in fact I'm using it myself ;-)
>
> Still, Grizzly-1.9.x is a PITA as a NIO framework, go for it only if you
> need HTTP support. And even in this case considering good responses about
> 2.x may be it'll be wiser to start from Grizzly-2, AFAIK it is supposed to
> be released soon. 1.9.x branch has too much problems and probably many of
> them will be resolved (or already resolved) only in 2.x because of the
> backward-compatibility requirements for 1.9.x.
>
>
>> You still need to lear a
>> little bit of NIO with 1.9.x
>>
>
> True but this is not the main issue. Much bigger problem is that you'll need
> to learn EVERYTHING about Grizzly internals if you want to write something
> just a bit more complex than shown in the tutorials. BTW, this is another
> problem with Grizzly-1.9.x - docs/tutorials are scarce and half of them are
> plain wrong (for the most part because they are outdated but some were
> wrong from day 1), so you'll need to dig up everything in the source code
> yourself. I feel that it is completely wrong when a programmer in order to
> _use_ framework need to know _everything_ about its _internal_
> implementation details.
>
> I have a 1.5 year experience with Grizzly 1.7.x-1.9.x, so this is not some
> first look opinion.
>
> Alexei
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
>