Socket/Server problem how to make it with at least 1000 connetions

Question

0.00/5 (No votes)

See more:

Hello,

I want to know what technology to use in creating a Chat application in C#, a server and a chat client for the possibility to maintain a minimum of 1000 users logged in at the same and chatting. I have created a application like this with TcpClient, BinaryReader and Writer but when around 250 users connects i receive a message like "the connection was forcibly closed by the remote host". The server is done in this way: when a users connects to the server i create a TcpClient and a thread in witch i am waiting in a try catch and in a while for the message that user can send.

If you want some code please ask.Thanks

Regards,
Sas Gabriel

Posted 14-Dec-11 8:47am

Gabriel Sas

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 · Accepted Answer · 2011-12-14T09:06:00

Solution 1

First idea you should never play with is creating variable number of threads, something like a thread per client. Don't even think about it! It is absolutely excessive and can kill your service. For a basic network service based on TCP and multiple channels, you need to create just two network threads: one listening for new connections, another one reading/writing from/two network stream to implement your application-level protocol.

You can find a quick sketch of such design in my past solutions:

Multple clients from same port Number[^],
automatic updater triggered via server[^].

Please also see the links to other related solutions in these posts.

Good luck,

—SA

Posted 14-Dec-11 9:06am

Sergey Alexandrovich Kryukov

Comments

Gabriel Sas 14-Dec-11 15:32pm

Nice explanation about how this server should be, now i know in witch direction to go and search about the rest of the information i need. But in this server design i dont understand one thing:

Gabriel Sas 14-Dec-11 15:32pm

the thread with the tcplistener.acceptclient is very clear to me, but in the other thread how do i receive a message from multiple users? because if i have a BinaryReader read; and i am doing message=read.ReadString(); it blocks and waits until a message is receive, in witch way to implement this?

Sergey Alexandrovich Kryukov 14-Dec-11 18:00pm

On every accept you receive a socket (through AcceptSocket) or an instance of TcpClient (through AcceptTcpClient), a server object representing remote socket of the connected client. If you work with socket, call its send/receive, if an instance of TcpClient, get a string from it its GetStream and read/write from/to it.

Is it clear?

Also, don't call async APIs as you already use stream and can call blocking APIs in a sequential manner.

It's important to understand the nature of client socket or instance of TcpClient instance. Once connected, it comes in two instances on different processes: one on client, another on server, with one-to-one correspondence. TcpListener does not participate in communications themselves, it only listens/accepts.
--SA