http://www.flashorb.com/articles/soap_vs_flash_remoting_benchmark.shtml
But more importantly, all the flash remoting servers can invoke methods
on webserices and return the results to the flash client in a binary
format. This seems to be forgotton by most for some reason. The only
difference, the webservice is being deserialized on the server instead
of the client. This is a good thing. MM is pushing clientside webservice
deserialization for those who do not have access to their server. At
least, thats the only reason I can see why you'd use it. Of course, if
you don't have access to the server publishing the webservice I doubt
you can change the crossdomain.xml and if you can't change that then you
can't consume any remote service from flash. The moral of the story?
Native client web services api looks good on the box and ppl buy into
it.
-----Original Message-----
From: Matt Liotta [mailto:[EMAIL PROTECTED]
Sent: January 30, 2004 7:05 AM
To: CF-Talk
Subject: Re: Web Services vs. Remoting - Performance Tests?
My tests have shown that Flash Remoting is significantly faster for
large amounts of data, but only when HTTP compression is not used with
SOAP. I believe that SOAP plug HTTP compression strikes the right
balance of standards and performance.
-Matt
On Jan 30, 2004, at 9:36 AM, Burns, John wrote:
> Has anyone seen real, objective performance tests done on web services
> and flash remoting that compare the speed differences and would help
me
> make a choice on whether it's just as easy to use web services in
Flash
> as opposed to remoting? I know that technically remoting is faster,
> but
> I'm curious by how much. Any info would be great. Thanks!
>
>
> John Burns
>
_____
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
