Couple of questions about socket

well im using public source so there is high probability that its socket system sux so i have couple of questions about that :

1st - from where i can learn to code socket system myself ?

2nd - the npcs of the source contains high amount of useless Checkers so if i deleted them would they affect the Socket ?

3rd - How the console crashes when alot of players Play in server ??

1. MSDN. [Only registered and activated users can see links. Click Here To Register...] - if you want to get a real in-depth explanation about sockets - beej.us/guide/bgnet/
2. No.
3. That could be anything.

The link Lateralus posts and...

Server:
[Only registered and activated users can see links. Click Here To Register...]

Client:
[Only registered and activated users can see links. Click Here To Register...]

Also the e-book I released covers sockets and not only winsoc.
[Only registered and activated users can see links. Click Here To Register...]

And at last my guide:
[Only registered and activated users can see links. Click Here To Register...]

Also 2.

The socket system is not getting affected by your source in any other way than connections and packethandling and usually you invoke events, so the actual socket system is neither effected there. Usually it's not the sockets that's the big problem, but the way packets, threads and features are getting handled.

3.
Lolwut?

Quote:

Originally Posted by shadowman123 well im using public source so there is high probability that its socket system sux so i have couple of questions about that : 1st - from where i can learn to code socket system myself ? 2nd - the npcs of the source contains high amount of useless Checkers so if i deleted them would they affect the Socket ? 3rd - How the console crashes when alot of players Play in server ??

1. Examples, Research and Practice.
2. Checkers... as in selection statements? And no. The socket system manages incoming and outgoing packets.
3. Well there's your problem.

Quote:

Originally Posted by Fаng 3. Well there's your problem.

Not quite. No one wants to release something that's not working as good as they could make it work. Whenever someone releases something (that was written by their hands) they want it to show everyone/give everyone an example. You are wrong.

Quote:

Originally Posted by -impulse- Not quite. No one wants to release something that's not working as good as they could make it work. Whenever someone releases something (that was written by their hands) they want it to show everyone/give everyone an example. You are wrong.

Where in "There's your problem" did I say that people were going to give him a good source? o.O

Quote:

Originally Posted by Fаng Where in "There's your problem" did I say that people were going to give him a good source? o.O

No, but unless those who released sources wanted to make a fool out of the users then yes that would be a problem but I am not sure nor aware of people in this community who releases sources to steal or w/e.

I am just saying that when people put something on the internet they do because they either want to show the world how much they improved or because there's nothing on the web that can be used for nice performances.
Public source doesn't mean bad source.
As long as the sockets in a source work then that's all you have to know, unless the one who wrote the sockets does some shitty things with the data received before passing it to the packet handler then yes, I believe that's your problem, otherwise the problem is just somewhere else.