Have Geek Brain

Strategy for WCF server with .Net clients and Android clients?

I am using WCF to write a server that needs to be able to communicate with .Net clients, Android clients, and possibly other types of clients.

  • The main client type is a desktop application that will be written to .Net. Typically, this client is on the same intranet as the server. It will make an initial call to the server to get the current state of the system, and then will receive updates from the server when the value changes. These updates are frequent, perhaps once a second.

  • Android clients will connect over the Internet. This client is also interested in updates, but it is not as critical as the desktop client, so a (less frequent) polling scenario might be acceptable.

  • All customers must be logged in to use the service, and when connected over the Internet, the connection must be secure.

I'm familiar with WCF, but I'm not sure which bindings are most appropriate for the scenario and which security solution to use. Also, I haven't been using Android, but I would like to keep it as simple as possible for the person implementing the Android client to consume my services. So what's my strategy?

+2


a source to share


2 answers


with the small size android i made.

Android sdk doesn't support soap server, you need to write it all yourself.



Rest is your only option when working with WCF and Android. How Google is pushing you to develop apps.

0


a source


WCF over HTTP transport is the way to go because it is not binary and does not make the assumption that all peers are .net / windows.



see this page for more information

0


a source






More articles:


All Articles