Good points, Robert - I hadn't considered those use cases at all, just consumer-facing web applications (and I've seen web services abused for that use case many times.)
Thanks, Aral On 4 Nov 2006, at 18:31, Robert M. Hall wrote: > Hey Aral, > > You have some valid points, I defnitely agree with you on services > that may > need additional security, or services that you don't want to expose > to the > general net population. Also agree where projects have very large > queries > and the size of the SOAP overhead outweighs the actual data being > sent. I > also love AMFPHP, but I still get a lot of mileage out web services > in Flash > for a variety of uses, couple examples: > > 1. Quick prototypes of applications while the services are still being > developed on the server side. It allows quick iterative development > while > both teams (server side / client side) can work separetly or in > tandem with > minimal communication necessary between teams. > > 2. Internal/private applications not exposed to the general net, that > require periodic maintenance. I've found that web services are > pretty easy > to follow even for intermediate to novice Flash developers. > > 3. Closed system applications - kiosks, interactive exhibits, or > other types > of apps where the system is a closed loop and the environment is > totally > controlled. > <snip> _______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
