Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of dave2wave@comcast.net
 designates 76.96.30.64 as permitted sender)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1084)
Subject: Re: BlazeDS
From: Dave Fisher <dave2wave@comcast.net>
In-Reply-To: <CB2DE2E5.3959D%aharui@adobe.com>
Date: Tue, 10 Jan 2012 19:50:33 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <BCB8779B-CA4F-4D0F-9F71-C12F87C1CB60@comcast.net>
References: <CB2DE2E5.3959D%aharui@adobe.com>
To: flex-dev@incubator.apache.org


On Jan 7, 2012, at 11:54 AM, Alex Harui wrote:

>=20
>=20
>=20
> On 1/7/12 2:02 AM, "Anne Kathrine Petter=F8e" <yojibee@gmail.com> =
wrote:
>=20
>> =46rom the top of my head:
>> Would you be able to get enough initial committers for a proposal?
> That's one thing I'm worried about.
>=20
>> there someone championing the project at ASF?
> Are you volunteering to be champion?
>=20
>> I don't know how many external contributors you have today?
> Probably zero today.
>=20
> I guess some folks are willing to work on it, but what needs to be =
done to
> it?  And does it matter to Apache if it only needs a few minor tweaks =
and
> isn't very active?

Speaking with a developer hat (not a mentor hat):

My day$ work has been document creation and project management, for =
decades. Our work stack produces highly annotated Postscript, PDF, PPT, =
PPTX, XLSX, SWF, and PNG output. These are served with JSP, HTML and =
Java servlets on Apache Tomcat. The SWF creation is via Transform SWF =
from PS pages. We've contributed to Apache POI including some graphic =
support in PPT, PPTX, and XLSX generation in Java.

Having an available BlazeDS server library to adapt to our platform =
would make Apache Flex a more attractive application delivery platform. =
It would make it a feasible choice that I could probably sell, mobile is =
important!=20

On another note adding a blaze namespace to MXML on a par with spark =
while simplifying the specification of web services from the client =
application end would be great. I think this would be in good alignment =
with Apache Flex as an SDK.

Just some thoughts... IMO to me a Blaze is what you get from a Spark :-)

Regards,
Dave