> In what way ?
> It seems to talk SOAP, JavaRPC and several others.

I can't speak for their latest release emerging but previous versions
had little infrastructure available in this area.

> What do you mean by remoting here ? How is that different
> from 'remote
> service' ?

SOAP vs MM's Protocol.

Inherently a flash player weak point but remoting protocol offers
significant performance boost over SOAP. (in real world, I'm not making
an academic claim here) Perhaps the latest release supports it, don't
know.

I'd suggest taking both for a spin in a real world app scenario. Devil
is in the details...I can attest to that coming from traditional flash
RIA background then trying Laszlo and eventually settling on Flex.

As for price, it's not our primary concern. Of course we'd rather pay
less but our 2 machine cluster will support a large array of RIAs going
forward. In comparison to actual development costs (regardless of the
technology used) the sticker price is a small fraction of that cost. My
point being our decision to remain on the flex train comes down to a
combination factors other that the price tag. Both Developer and User
experience with the technology, time already invested  in tech ramp up,
stability of the product, reputation of the company driving the product,
responsive to our requirements input...etc

We're certainly nobody special in the thick of things yet we often have
direct access to MM engineers and product folks who are taking our input
directly into the product. That kind of communication is critical for
us...and is available to anyone really on flexcoders.

To summarize. I've done my in-depth comparison and found Flex to be well
beyond their implementation. I'll brush up on Laszlo's latest offering
but it'd take a helluva push to move us of our current path.

Cheers!
Stace
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings] [Donations and Support]

Reply via email to