check this out before you decide...
http://www.flashorb.com/articles/soap_vs_flash_remoting_benchmark.shtml
but based on the numbers there I am never using webservices again until
they fix this crap. actually i am considering taking up an entirely new
field after working with flash for 5 years now. the crap that macromedia
keeps dishing out is really getting to me at this point.
well that was one long article just to say there was a memory leak in SOAP that was fixed by a patch...
but the article, at the very end, does say "the Flash Remoting approach is by far more stable and has better performance" than SOAP.
you wouldn't use SOAP anyway... as ASP uses AMF (action message format), not SOAP, to perform the remoting. as explained in this document...
http://livedocs.macromedia.com/flashremoting/mx/Using_Flash_Remoting_MX/intro2.h
tm#1176427
here is a quote by Tom Muck... "..if you do have access to the server, you won't want to use SOAP..."
http://www.flash-remoting.com/articles/fr2004pt1.cfm
and here .... "The use of verbose XML in SOAP, for example, makes a web service call using SOAP about 400 percent bigger than a similar call to a Flash Remoting service, which uses a terse binary format (AMF or Action Message Format)."
http://www.oreillynet.com/pub/a/javascript/2003/09/16/flashremoting.html
and finally... here is an article that discusses asp and remoting...
http://www.macromedia.com/devnet/mx/flashremoting/articles/intro_flremoting_net.html
enjoy,
dutcheese
Leland - 26 Dec 2003 13:59 GMT
presumably fixed cheese...i haven't seen a benchmark after the update to
show that they actually did fix the leak. it has been my experience that
macromedia says a lot, but doesn't always do.
> well that was one long article just to say there was a memory leak in SOAP that was fixed by a patch...
>
[quoted text clipped - 14 lines]
> enjoy,
> dutcheese