Atmosphere 0.5 Roadmap: Client side, new Filters, etc...Time to speak!

[Jeanfrancois Arcand]

Salut,

I would like to start getting feedback from the community and decide
what we must have with Atmosphere 0.5.

So far we have (some have issues, some don't...I will file them once we
agree)

Must Have
---------

+ Output some HTML comments by default for browser that needs some bytes
to handle suspended connections
     https://atmosphere.dev.java.net/issues/show_bug.cgi?id=13

+ Transaction support: When doing long polling or streaming, some events
might get lost between reconnection. Adding a special header and or
cookie to track which evens was delivered and which failed will helps
reducing lost of events

+ Persistence Support: I would like to have persistence of events
support, e.g we should have a BroadcastFilter than persists the events
so they can be retrieved later. I've discussed with the Derby team and
we may get some help from them :-) The idea is to avoid any events lost,
and to be able to allow tracing/querying events.

+ Paul & Viktor has both proposal on how we need to handle the @Resume
state. I will let them expose their proposal.
   * http://is.gd/4GmwK

+ Aggregate Filter: Under high load, broadcasting events might kill
performance and we may ends up having to write too many event in a short
amount of time. I would like to have a BroadcastFilter/Serializer that
allow aggregation of events, so they can be written in one chunk instead
of several. This is easy to implement, but we need to find some rule
when the Framework should shift to that mode.

+ JMS based BroadcastFilter, like ShoalFilter and JGroupsFilter.

+ Injection of Atmosphere Object based on Paul's proposal:
   * http://is.gd/4GmtE

+ General Framework improvement, improve documentations, etc.

_ Lift Integration. Replace Jetty Continuation.

Should Have
------------

+ We need to start on a client side library, either by extending
JQuery/whatever javascript framework,JSF (already in PrimeFaces),
Wicket,Lift or by at least have some guidance and a how-to/white paper
to get peoples started.

+ Terracotta support

+ Bugs fixing

I would like to target December 2009 as a possible release date, but
like for 0.4, we must be flexible :-)

What peoples thinks?










---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Jeanfrancois Arcand]

Jeanfrancois Arcand wrote:

> Salut,
>
> I would like to start getting feedback from the community and decide
> what we must have with Atmosphere 0.5.
>
> So far we have (some have issues, some don't...I will file them once we
> agree)
>
> Must Have
> ---------
>
> + Output some HTML comments by default for browser that needs some bytes
> to handle suspended connections
>     https://atmosphere.dev.java.net/issues/show_bug.cgi?id=13
>
> + Transaction support: When doing long polling or streaming, some events
> might get lost between reconnection. Adding a special header and or
> cookie to track which evens was delivered and which failed will helps
> reducing lost of events
>
> + Persistence Support: I would like to have persistence of events
> support, e.g we should have a BroadcastFilter than persists the events
> so they can be retrieved later. I've discussed with the Derby team and
> we may get some help from them :-) The idea is to avoid any events lost,
> and to be able to allow tracing/querying events.
>
> + Paul & Viktor has both proposal on how we need to handle the @Resume
> state. I will let them expose their proposal.
>   * http://is.gd/4GmwK
>
> + Aggregate Filter: Under high load, broadcasting events might kill
> performance and we may ends up having to write too many event in a short
> amount of time. I would like to have a BroadcastFilter/Serializer that
> allow aggregation of events, so they can be written in one chunk instead
> of several. This is easy to implement, but we need to find some rule
> when the Framework should shift to that mode.
>
> + JMS based BroadcastFilter, like ShoalFilter and JGroupsFilter.
>
> + Injection of Atmosphere Object based on Paul's proposal:
>   * http://is.gd/4GmtE
>
> + General Framework improvement, improve documentations, etc.
>
> _ Lift Integration. Replace Jetty Continuation.
>
> Should Have
> ------------
>
> + We need to start on a client side library, either by extending
> JQuery/whatever javascript framework,JSF (already in PrimeFaces),
> Wicket,Lift or by at least have some guidance and a how-to/white paper
> to get peoples started.
>
> + Terracotta support
>
> + Bugs fixing
>
> I would like to target December 2009 as a possible release date, but
> like for 0.4, we must be flexible :-)
>
> What peoples thinks?
>
>

Hit the send too fast. Under Should Have

+ Allow configuration of the Web Server that runs the
AtmosphereSpadeServer. Right now it's Grizzly, but we should have an SPI
that allow others to plug in, like Netty, Jetty, GlassFish v3, etc. (Did
I really propose to remove Grizzly ;-))

A+

- Jeanfrancois

>
>
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]