how duplex communication between Sever and Clients in Asp.net Application

Question

0.00/5 (No votes)

See more:

ASM

I want duplex communication between Sever and Clients.

My Server PC have web Application And On my Clients PC Have local DB and windows Application. if my Clients do some transaction using window application ,I want to know the updated form of Data of Clients Local DB(SQL server).

Note 1) Client PC using Router base Internet ,Mean the IP of Client PC Is Change after hour or sometime after 24 hour,because its not Static .its Proxy IP (Public IP) Note 2) Client PC is not on LAN network. and i don't want its too.

NOTE 3) I don't want to allow Remotely Access on Client SQL SERVER.

NOTE 4) Clients Are more than 100 and Not on LAN or work group.(e.g one client in usa,one client in UK and one in France and so on) ,they are using a same Window application.

Note 5) Clients PC can access Server via Services.But Problem is Server can't access Client Pc cuz of Clients pc having Dynamic IP,not static ip Due to Router use..

Please give me Good Trick to handle this Type of Issue. what should i use in my Server Web application for dublix communication with Clients...websercvices or SingleR or WebSocket or any trick in your mind ? the main issue i can't get static ip of Client pc via internet connectivity.so what should i do now??

Thanks you !

Posted 20-Nov-14 6:35am

Tariq Mehmood

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2014-11-20T06:56:00

Normally, Web applications are not designed for duplex communications. Originally, HTTP was designed to support pure client-server. The problem here is to have server push. Please see my past answer discussing related problems and the articles referenced below:
Application 'dashboard' for website accounts[^],
http://en.wikipedia.org/wiki/Client-server_model[^],
http://en.wikipedia.org/wiki/Server_push[^],
http://en.wikipedia.org/wiki/Pull_technology[^].

However, there are some ways to work around the problem; they are not very simple. First, you can think about having a duplex Web Service. Please see this CodeProject article: Duplex Web Services[^].

You can also consider using some of the server push approaches, in particular, SignalR (please see the links in my past answer referenced by my first link above).

—SA