On Jan 8, 2012 12:31 AM, "Alex Harui" <aha...@adobe.com> wrote: > > Hi Doug, > > Do you have any idea what you would contribute?
I'm not sure off the top of my head, but I do know in the past, I have had the need for customizing BlazeDS and had to monkey patch the rpc components. I believe those customizations are even still in use. One small example is how the rpc framework is poor at communicating some information about reconnecting status. In regards to ideas, I would reach out to those I already know use BlazeDS and round up a much community I could to get their feedback. Especially given that > rpc.swc is in the Flex contribution? > > Or maybe one goal would be to move rpc.swc to this new project and make it > the umbrella for all server-side work? This it's my only hesitation to spin BlazeDS into it's own project. But my concern with leaving remain with the Apache Flex project is branding and release management. I think if we can build a community for BlazeDS (which I believe there is already a silent one, and silent only because contributions to Adobe was poor at best) then the separate protect could thrive - of course not as lively as this group, but good enough to survive. I'm still unclear how to address rpc.swc. maybe it would be good to move it over and make it completely part of the server-side umbrella, but my concern there would be that it would miss a good set of talented committers from here. So I think it's better suited to stay in the Apache Flex protect for that reason. Last thing on this note, if we do bring BlazeDS into Apache Flex, how will release management take place, and how will the product remain to be its own within another product? Especially since its an a optional server-side technology where there are others to choose from? >If we manage to get permission to > contribute parts of LCDS at an even later date, it would go in the same > project? I would think so. And that would be awesome to see contributions from LCDS! - Doug
