Java Socket or SocketChannel
I am designing a server for a remote file store in Java and trying to decide whether to use asynchronous java.nio.SocketChannels or the older blocking model with Sockets. What kind of factors should I consider when choosing between these two server architectures and what kinds of tasks would be better suited to one versus the other?
Multi-threaded winforms with multiple child forms using sockets
I develop application with two main option grouped by groupBox in main form. First option is run server with specific behaviour for example I choose TCP protocol, type IP address, port number and atfter that I click run button which generate independent forms with this specific server. Second option is client which is analogous to first option. Client and server can send/receive information to via sockets.
Why can’t sockets be used to identify individuals instead of cookies?
Another question was asked regarding the use of IP addresses to identify individual clients. I think I understand why an IP address is insufficient. But what about the socket, which has more information and, from what I understand, is stateful? Couldn’t that be potentially used in lieu of a cookie?
Is it possible to send arbitrary data (not TCP or UDP) through a socket, while allowing the kernel to do the IP encapsulation for me?
Suppose I want to implement my own transport layer protocol. If I open a socket with:
How inter-process communication is handled on .NET Core?
I have to implement a bi-directional communication between two local process with support to backward compatibility .NET Core/NET Framework and platform architecture x86/x64.
The options that i have explored so far are: