Basically every webcontainer these days supports GZIP compression. We use Tomcat in many circumstances which is hyper configurable. We can actually tell it to only compress the SOAP traffic and to do so when it exceeds N bytes etc. So in effect we turn SOAP into a compressed binary format. That makes that differential much less relevant.
-- Dave Wolf Cynergy Systems, Inc. Adobe Flex Alliance Partner http://www.cynergysystems.com http://www.cynergysystems.com/blogs Email: [EMAIL PROTECTED] Office: 866-CYNERGY --- In flexcoders@yahoogroups.com, "Tom Lee" <[EMAIL PROTECTED]> wrote: > > I'm sure someone already pointed this out, but network latency is also a > factor. AMF is a compressed format, so it can load faster and in that sense > make your app more responsive. With XML web services, the tags themselves > add a degree of overhead. There are schemes for compressing web services > which can help. > > -----Original Message----- > From: flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] On > Behalf Of Martin Wood > Sent: Wednesday, August 23, 2006 11:27 AM > To: flexcoders@yahoogroups.com > Subject: Re: [Junk E-Mail - LOW] [flexcoders] Re: Choice of backend systems > - which provides > > > > Jack Caldwell wrote: > > Martin: > > > > OK . . . . so the lag time is when the data gets back to the end-user? > > exactly, its the time it takes for the flash player or actionscript code to > convert the incoming data into a format usable by the application. > > Before in the flash world that was a big deal as XML processing was > expensive > and often tedious to code whilst remoting was natively implemented and > provided > you with typed business objects as a result of the call. > > With Flex 2 the differences are not so important as the features like data > binding and e4x pretty much level the playing field for the data formats. > > > > Bottom line . . . . with all things being equal . . . . > > > > Does a web service request take longer to process on the server than > > a AMF request? > > > > If the answer is . . . . in general yes, then that can be an issue with an > > increase in users. > > > > If the answer is . . . . it depends on the data being requested and/or the > > data format then that seems to suggest that everyone must run tests to > > compare results and then test again based on scaling up. > > I suppose one of the main factors would be the server code that handles the > incoming request and then transforms the business data into the required > format > to send back to the client. > > That could be anything from some hand written php code to a commercial > remoting > gateway. > > Its so context dependent that its impossible to make a general statement of > the > type 'Remoting performs better than Web Services' > > It would be interesting to see a comparison of the throughput you could > expect > when comparing different solutions on the same server hardware, e.g. PHP > Nu-Soap against AMFPHP.. Jrun's remoting vs. OpenAMF vs JAX-WS etc.. > > and where they each perform the same business operation and return the same > data.. > > but then there are other concerns such as memory usage and what else the > server > is used for and how it performs for those use cases. > > thats what i mean by you have to take it on a case by case basis. > > :) > > martin > > > -- > Flexcoders Mailing List > FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt > Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com > Yahoo! Groups Links > -- Flexcoders Mailing List FAQ: http://groups.yahoo.com/group/flexcoders/files/flexcodersFAQ.txt Search Archives: http://www.mail-archive.com/flexcoders%40yahoogroups.com Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/flexcoders/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
