lenniep
lenniep

Reputation: 739

Client-Server architecture

This topic has been discussed million times before, but let me clarify my needs: I need a single server which controls a system and includes the necessary functions. Furthermore, there will be "n" Clients which represents only the HI/GUI and call server side functions. The server itself should be able to send data back to the clients and call client-side functions too (like shutdown, exit and so on...)

I have heard about duplex services/contracts (http://msdn.microsoft.com/en-us/library/ms731064.aspx), but I'm not sure how far I'll come with that. How would you handle this?

Upvotes: 0

Views: 922

Answers (2)

John Petrak
John Petrak

Reputation: 2928

I recently made a proof of concept app that made both the server and the client host a WCF service each. The client connects to the server and then in a handshake call, gives the server the connection information to allow the server create a separate connection back to the client. It worked a treat with multiple clients on network links from local lan to 64k line on remote sites at the same time.

Upvotes: 2

lasseeskildsen
lasseeskildsen

Reputation: 609

You could use WCF, and host the service on the server in IIS, in the application on the client and let the client register it's endpoint on the server.

Upvotes: 0

Related Questions