Thread per client? Headless server?

You could look into packages that handle this for you, like RakNet.

You could look into packages that handle this for you, like RakNet.

I know about those layers, I really want to build my own one.

Maybe I don't really understand what you're asking, but will select() not work for you? You could have select() operating on all the client sockets in one thread, and pass the data from the clients to your main thread via messaging.

I would think you've already looked at that option, but, it's the simplest way of asynchronously gathering data from any number of clients and sending to a control thread.

Hey there.

I'm trying to build a server for my humble online game in C++ right now,
and I ran into a problem.

From what I can tell, there are several ways to manage clients and read data from them.
I'm looking for a convenient way to do so, without the need of creating a window (for asynchronous data management i.e)
and I also need a way that will be efficient and stable.

Iv'e tried to read data from client in a thread-per-client way and it didn't seem to my likings, is there any other
traditional way to do so? If so, I'd be happy if you pointed me to a guide or whatever.

Thanks in advance, Tamir Atias.

Moderators/Administrators: Sorry for posting this in the wrong forum, can anyone please move this?

Maybe I don't really understand what you're asking, but will select() not work for you? You could have select() operating on all the client sockets in one thread, and pass the data from the clients to your main thread via messaging.

I would think you've already looked at that option, but, it's the simplest way of asynchronously gathering data from any number of clients and sending to a control thread.
[quote name='Kono' timestamp='1297024991' post='4770582']
Hey there.

I'm trying to build a server for my humble online game in C++ right now,
and I ran into a problem.

From what I can tell, there are several ways to manage clients and read data from them.
I'm looking for a convenient way to do so, without the need of creating a window (for asynchronous data management i.e)
and I also need a way that will be efficient and stable.

Iv'e tried to read data from client in a thread-per-client way and it didn't seem to my likings, is there any other
traditional way to do so? If so, I'd be happy if you pointed me to a guide or whatever.

Thanks in advance, Tamir Atias.

Moderators/Administrators: Sorry for posting this in the wrong forum, can anyone please move this?

[/quote]

So basically, when there is data available for reading, I need to inform the client with the same socket about it?

Thanks for you answer.

Please do not delete content in threads. The thread will continue to exist in case there is any additional discussion required on the subject.

I cannot find the original title so I've given it one based on the original post. I've also moved it to the appropriate forum.

The FAQ for the networking forum is a good place to look for this information, too!

[color=#282828][font=helvetica,arial,verdana,tahoma,sans-serif]

Hey there.[/font]

[color=#282828][font=helvetica,arial,verdana,tahoma,sans-serif]

I'm trying to build a server for my humble online game in C++ right now,[/font]

[color=#282828][font=helvetica,arial,verdana,tahoma,sans-serif]

and I ran into a problem.[/font]

[color=#282828][font=helvetica,arial,verdana,tahoma,sans-serif]

From what I can tell, there are several ways to manage clients and read data from them.[/font]

[color=#282828][font=helvetica,arial,verdana,tahoma,sans-serif]

I'm looking for a convenient way to do so, without the need of creating a window (for asynchronous data management i.e)[/font]

[color=#282828][font=helvetica,arial,verdana,tahoma,sans-serif]

and I also need a way that will be efficient and stable.[/font]

[color=#282828][font=helvetica,arial,verdana,tahoma,sans-serif]

Iv'e tried to read data from client in a thread-per-client way and it didn't seem to my likings, is there any other[/font]

[color=#282828][font=helvetica,arial,verdana,tahoma,sans-serif]

traditional way to do so? If so, I'd be happy if you pointed me to a guide or whatever.[/font]

[color=#282828][font=helvetica,arial,verdana,tahoma,sans-serif]

Thanks in advance, Tamir Atias[/font]

[color=#282828][font=helvetica,arial,verdana,tahoma,sans-serif]

[restored deleted content --rip-off] [/font]

Its prefered not to use thread per client connection because of the thread switching overhead and you will
have to interlock the game data to prevent the threads from doing partial writes before being interrupted.

select() with a single thread will self synchronize the network operations (you still may need to do some interlocks with a main game thread)