|
|
Posted by Andy Dingley on 10/10/49 11:22
On 27 Jul 2005 03:40:28 -0700, "Travis Newbury"
<TravisNewbury@hotmail.com> wrote:
>Why would you have to do 3 implementations?
Three implementations - good.
Effort of doing three implementations - bad.
Lets see how we put the business logic in our three different places: on
the server at form submission time, on the client, and on the server and
being used interactively by the client (through AJAX).
Now you can do any of these through a Flash-based front end too (been
there, did that with XML-RPC a couple of years back). But the problem is
that you're writing new code for each one. The first is in J2EE (or
whatever), and the second is in pure Flash. There's no way to go from
one to the other without re-coding by hand. The third one is even more
awkward - you need to integrate the two platforms and you're all on your
own for how to do it.
AJAX is a defined route. No matter how I back end it (apart from .Net,
which will obviously get it deliberately wrong) then I'm looking at the
same AJAX platform. From my client-side code, I see the same tools and
interface to code to. From the back end I see an integrated path that
can migrate my business logic almost dynamically, on demand of the user
and their particular platform capabilities for that session.
Navigation:
[Reply to this message]
|