SupahFly.net he is from all over the globe your i have like to have the same right as wonder if anything

C# RSPS Update #1

Since this whole thing is much of a learning experience for me it is assumed that I lack knowledge of something and I am trying to gain this knowledge. The lack of knowledge here is of client-server applications.

Asynchronous I/O is probably a good idea
So while it's odd that I am learning the difference between synchronous and asynchronous (non-blocking) I/O it's good that I am learning about it. I guess my inexperience when it comes to client-server programming coupled with the bad private server sources out there gave me the idea that everything must waste time.

That is not true with this, and I'll explain why. Synchronous blocks and asynchronous does not. Because of blocking you would need to update everyone at the same exact time on a different thread to avoid stopping the servers function.

Let's say you initiate a connection, you are then like "hi stream!!! read a byte!" It then stops on that code where you said "read a byte!" and waits for there to be a byte available to read and then resumes. This is blocking.

Let's say you initiate a connection, you are then like "hi stream!!! tell me when you have a byte to read!" It then lets you resume your normal tasks until it has a byte to read. Once it has that byte to be read it will interrupt your current process like Kanye West and call some cool method in your code that will read that precious byte from the stream.

It makes sense for it to only tell me that there's data to be read instead of going through all the sockets and being like "yo doq you got some data yo hook me up son."

Sure my examples and explanation may be a bit amateur but that only makes it apparent that I haven't done my tests yet! I'll know for sure what the fuck I'm talking about once I do some tests to help me wrap my head around (not literally, although that would be cool) this all.