In .Net, the System.Net.Sockets namespace provides a managed implementation of the Windows Sockets (Winsock) interface for developers who need to tightly control network access. All other network access classes in the System.Net namespace are built on this socket implementation. The TCPClient, TCPListener, and UDPClient classes encapsulate detailed information about creating TCP and UDP connections to the Internet; the NetworkStream class provides For the basic data flow of network access, Socket can be seen in many common Internet services, such as Telnet, HTTP, Email, Echo, etc. Although these services have different definitions of communication protocols, their basic transmission uses Socket. In fact, Socket can be regarded as a data channel like a Stream. This channel is established between the application (client) and the remote server. Then, the reading (receiving) and writing (sending) of data are both for through this channel.
It can be seen that after creating a Socket object on the application side or server side, you can use the Send/SentTo method to send data to the connected Socket, or use the Receive/ReceiveFrom method to receive data from the connected Socket. Data;
For Socket programming, the .NET Framework's Socket class is a managed code version of the socket service provided by the Winsock32 API. There are a number of methods provided for implementing network programming, and in most cases the Socket class methods simply marshal the data to their native Win32 copies and handle any necessary security checks. If you are familiar with Winsock API functions, it will be very easy to use the Socket class to write network programs. Of course, if you have never been exposed to it, it will not be too difficult. Follow the explanation below and you will find that using the Socket class to develop windows
There are rules for web applications, and they follow roughly the same steps in most cases.
This section introduces the use of Socket to implement a high-performance asynchronous UDP server. In fact, UDP does not distinguish between clients and servers. , but sometimes we communicate with the server using UDP.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 |
|
Session Encapsulation Class
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 |
|
Socket Asynchronous UDP Server Event Parameter Class
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 |
|
The above is the C# network programming series Article (5) Socket implements the content of asynchronous UDP server. For more related content, please pay attention to the PHP Chinese website (www.php.cn)!