Salut,
Richard Corsale wrote:
> Jeanfrancois,
>
> If you dont mind my asking, how do these regressions keep making their way back into the trunk?
It's the refactoring of Comet that caused that small glitch. Mainly, we
have removed the CometSelector that detect if a client close a
connection or used for async read/write I/) with Comet. I've reviewed
the code but missed that change.
Is it upstream patches that use older code re-merged?
No it's really new code. I guess we have learned something with the
recent refactoring. Don't refactor too much :-)
A+
--Jeanfrancois
>
>
> --Richard
>
>
>
> ----- Original Message ----
> From: Jeanfrancois Arcand <Jeanfrancois.Arcand_at_Sun.COM>
> To: dev_at_grizzly.dev.java.net; users_at_grizzly.dev.java.net
> Sent: Wednesday, April 29, 2009 10:40:12 AM
> Subject: 1.9.15 this Friday?
>
> Salut,
>
> we need to cut an official release of GlassFish v3 M2 release (JavaOne). The main issue we have are mostly a major regression with Comet (corrupted req/res) from our last 1.9.11 release, and Response.suspend/resume issue found by Rama
>
> Please post the issue you want to get fixed before Friday. Developer, try to fix as many issue as you can:
>
> http://is.gd/vmHx
>
> Thanks
>
> -- 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
>