Ultimately, you might be better off walking with what you know. Since you mentioned WCF, I assume that you have some .NET background, and it will be easier for you to develop in .NET than to learn a new language and framework. In this case, several options are offered:
- Go with WCF as it is the de facto standard in the Microsoft world for creating services. Recognize that with WCF you have the option to migrate using a SOAP-based service or a lighter weight RESTful service using WCF WebHttp. As mentioned in one of the other posters, you should probably go with WebHttp to avoid the overhead of SOAP.
- Look for an option like Adobe FluorineFx , which allows you to program in .NET and take advantage of Adobe's advanced remote access technologies and protocols (such as the AMF binary protocol) that are otherwise only available on the Java platform.
, , WCF SOAP WCF WebHttp- Flex. , , AMF, Java.