users@grizzly.java.net

Re: Async feature and its JavaDoc...

From: Richard Jackson <richard.jackson_at_gmail.com>
Date: Thu, 20 Nov 2008 20:59:34 -0600

You know what would be really nice is a wiki versas the blog where all
documentation/how-to's could be located.

Any ways just a thought as javadoc really is not designed for that
kind of stuff.

Richard

On Thu, Nov 20, 2008 at 12:35 PM, Jeanfrancois Arcand
<Jeanfrancois.Arcand_at_sun.com> wrote:
> Salut,
>
> huican ping wrote:
>>
>> That is great and thanks a lot.
>>
>> For the http module you are referring, is it the one "the Embeddable
>> HTTP WebServer binary source Javadoc Getting Started!" on the webpage.
>> Sorry for my ignorance.
>>
>
> Yes :-) I will clarify the index.html and add more information as I suspect
> this is a little confusing.
>
> A+
>
> -- Jeanfrancois
>
>
>>
>> On Thu, Nov 20, 2008 at 12:19 PM, Jeanfrancois Arcand
>> <Jeanfrancois.Arcand_at_sun.com> wrote:
>>>
>>> Salut,
>>>
>>> huican ping wrote:
>>>>
>>>> Hey Jeanfrancois,
>>>>
>>>> I have a quick question here.
>>>>
>>>> I noticed that one the web https://grizzly.dev.java.net/, there is a
>>>> link
>>>> for:
>>>> Grizzly 2.0 Framework (Work-in-Progress, Release Date 12/2008) binary
>>>> source Javadoc Getting Started!
>>>>
>>>> Does the JavaDoc for Grizzly 2.0 includes all the API interface for
>>>> async
>>>> feature?
>>>
>>> Right now it only include the core framework classes. The
>>> http/comet/cometd
>>> module aren't yet ported to use 2.0 instead of 1.9 (original grizzly
>>> framework)
>>>
>>>
>>> Or I should look somewhere?
>>>>
>>>> BTW, How well does the Grizzly 2.0 Framework support the async feature
>>>> if
>>>> you can give me some idea?
>>>
>>> 2.0 is a complete redesign of grizzly 1.x. Over the last 4 years we
>>> learned
>>> a lot from our users and we want to make a big steps and re-design from
>>> what
>>> we have learned. We are working hard to deliver the first stable version
>>> mid
>>> December.
>>>
>>>
>>> I believe it should be pretty well since "Embeddable Comet WebServer etc"
>>> based on those APIs working pretty good.
>>>
>>> At the Comet level, the API will stay the same as it build on top of the
>>> http module:
>>>
>>> |-------------Cometd ---------|
>>> |-------------Comet-----------|
>>> |--------Servlet Container----|
>>> |-------------http------------|
>>> |-----------framework---------|
>>>
>>> So theoretically, nothing should change in terms of Comet support.
>>>
>>> Did I understood you correctly?
>>>
>>> A+
>>>
>>> -- Jeanfrancois
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
>> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_grizzly.dev.java.net
> For additional commands, e-mail: users-help_at_grizzly.dev.java.net
>
>