Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of vanelord@gmail.com designates
 74.125.82.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CD401B37-07EE-4105-A980-D0B337B1A2BF@gmail.com>
References: <49562545$49da9aec$372d7e10$@com>
	<CD401B37-07EE-4105-A980-D0B337B1A2BF@gmail.com>
Date: Sat, 7 Jan 2012 13:58:01 +0100
Message-ID: 
 <CAKW9vdV7a_h3992AeYMyB2pmqMQ51csLqBSY8AZGnjGfEwSAaw@mail.gmail.com>
Subject: Re: BlazeDS
From: Michal Szczepanski <vanelord@gmail.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Content-Type: multipart/alternative; boundary=0016e6de00b1220c4d04b5efb7f9

--0016e6de00b1220c4d04b5efb7f9
Content-Type: text/plain; charset=ISO-8859-1

That's what ipod do with inappropriate hands.
One touch to disaster.
Sorry for spam

And now I need to say something, BlazeDS is also important for company I
work and more or less we depend on it now.
I'm interested in BlazeDS project as much as flex one.
I managed to get deep into all rpc.swc in flex (doing the lighter version)
and I'm sure it depends on BlazeDS like BlazeDS depends on flex ;)
However Blaze is server side technology and from my point of view should be
separated
and grow with server side things that can (but not necessary) overlap with
new flex features.
If community will be enough like Carlos Rovira said it could push flex
serverside forward
and flex could have full stack server side technology compete to LCDS if
possible.

2012/1/7 Carlos Rovira <carlos.rovira@codeoscopic.com>

>
> I would love to see little things like Enums supported, or have other
> things much more ambitious like LCDS functionality, but for me priorities
> are much more in the Flex client side that in Java.
>
> --
Michal Szczepanski

2012/1/7 Michal Szczepanski <vanelord@gmail.com>

>
>

--0016e6de00b1220c4d04b5efb7f9--