How do I get a message from client1 to client2 through a server using named pipes C#?

Question

0.00/5 (No votes)

See more:

I have a project that contains a C# console app, and a client WPF app. The goal is to have any one client write to the server, then the message is sent to all connected clients from the server. Currently, I can get many clients to connect to the server using threads on the server side. The problem is that when any client sends a message, only that same client receives the message back from the server. I've tried looking for help online but can't find anything that helps me communicate from the server to all clients.

I've tried to create a list of connected threads, and used a foreach() loop to send the message to all threaded clients, but it didn't work.

Any tips/help/ideas are welcome. I'm not looking for straight answers necessarily, maybe just help with what's needed to do it, and the sequence of events that need to happen.

Thanks

What I have tried:

server basics:

-wait for client to connect
-ifConnected -> create thread for connection
-put thread in a list
-in method for thread: loop ->
-receive streamreader input from client
-in foreach loop: write client message to server console, and use streamwriter to send
the message to all threaded clients in foreach loop

client basics (WPF):
-user types in message
-when user clicks on send button:
- use streamwriter to send message to server
- use streamreader to get message back from server
- display in textblock the messages from the server

Posted 10-Dec-17 15:08pm

Member 13568214

Updated 10-Dec-17 21:09pm

Add a Solution

Comments

PureNsanity 13-Dec-17 17:02pm

Is there a reason you have to use, or are limited to, named pipes?

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)

________________ · Answer 1 · 2017-12-10T21:09:00

One solution (simplest) - clients should have timer, and try to read from server messages every 1 second (or less, or more - according business demands).

Second - each client should be also server for main, and when main will have message from one client, it should broadcast this message to all connected clients, using its servers.