On Sep 27, 2007, at 8:05 AM, gers32 wrote:
First of all, a Flex front-end is Web 2.0 vs. Web 1.0 for JSPs. I
recently made the switch from JSP to Flex for that reason. Also, your
application will scale better if you put some of the logic inside the
Client.
I'm not so sure the "2.0 vs 1.0" argument makes sense. Flex is a
front-end technology. JSP is a server-side technology.
JSP composites the actual web page, in the sense that you still have
to build the "web page" that the browser will render (it could be
just plain XML as a result). Think of JSP as PHP, PERL, Python, Ruby
or whatever - just more complicated in my opinion.
JSPs can be used to deliver Flex applications:
http://labs.adobe.com/wiki/index.php/Flex_2_Tag_Library_for_JSP
Adobe's LiveCycle Data Services uses this for on-demand compilation
of MXML through JSP.
As for Bruce Eckel's article, that's exactly the one that convinced me
to skip AJAX and go directly from JSP to Flex. It also convinced my
boss...
I think you read that article wrong, or it was misleading (I didn't
read it that way). At least, the user responses show some people
don't understand these two technologies.
Flex/Flash and JSP have nothing to do with one another at the core.
JSP is just a way to separate presentation from dynamically generated
data on the server. It can be used to serve Flash content (through
flashvars), runtime compile Flex applications or use a combination of
HTML/DHTML/AJAX with the dynamic content.
You could just as easily use JSP to deliver an HTML page with an SWF
file and flashvars. Or, go the complex route and have it compile a
Flex app.
Java server pages, in the end, are java servlets. Nothing more,
nothing less. It's like any other server side technology that can
deliver a "page" to the user. What's delivered by that page is where
the discussion splits into the Flash vs. AJAX.
One cannot compare Flex (ie, Flash) and server-side technology. It
confuses me why it's brought up time and time again.
my 0.02,
Jon
