network limits

[gmysu]

Before i'll start doing something serious with sfml, i would like to know if threads will allow me to solve the 64 contections limit of the selector object.

so, will they?

cheers:)

[Laurent]

Yes, if you use multiple selectors, one per thread, you can work around this problem.

[gmysu]

thanks for your reply Laurent:). what if i create something like 1 thread - 1 client model? for lets say 1000 clients?

[Laurent]

1000 threads will kill your CPU. Don't forget that switching from one thread to another is a heavy operation.

[eXpl0it3r]

thanks for your reply Laurent:). what if i create something like 1 thread - 1 client model? for lets say 1000 clients?

I'm not sure what you want to do, but it sounds like you don't have that much knowledge on networking and that you want to do some crazy thing that would need 1000 clients or so.
I suggest you first dig deeper into the material and read some books on networking.

[gmysu]

thanks for your reply Laurent:). what if i create something like 1 thread - 1 client model? for lets say 1000 clients?

I'm not sure what you want to do, but it sounds like you don't have that much knowledge on networking and that you want to do some crazy thing that would need 1000 clients or so.
I suggest you first dig deeper into the material and read some books on networking.

oh its a small project, im just wondering if im able to put together something with more than 100 peers connected. i created two threads, where i placed blocking listener accepting connections in one of them, and loop that goes through connected clients in the other. 1000 threads was a sick idea, i must admit :> thanks for your help though:)

[Qix]

Coming from a networking background, I've personally set up a system using 'blocks' of clients. I usually set up an array of sockets in a struct (perhaps with some other header-type info about the block), and then have an array of those 'blocks' (along with some more optional header info).

The total number of clients you can support would be the number of blocks times the number of sockets in the block.

Each block is then given a thread. When you add/remove clients, check if the size is coming from/going to 0 and suspend the thread.

Make sure to set the clients to non-blocking, so you can just loop in that thread checking for each client.

This has been proven and works; however, not for SFML. I imagine the process would be similar, if not easier.

Just my 2 cents. Cheers!