3 ms·

I believe so. I don’t think either that or domain sockets are quite as ubiquitous as TCP sockets though. The issue I see with domain sockets is that although

by rusk 4mo ago

I believe so. I don’t think either that or domain sockets are quite as ubiquitous as TCP sockets though. The issue I see with domain sockets is that although they may be supported for example by spring, you can’t rely on a consistent cross platform experience which is perhaps (anachronistically?) a core ethic of the Java community. I would favour domain sockets as to make a component go from being embedded to networked would require a small but significant implementation step. But established best practice unfortunately disagrees with me.

inigyou 4mo ago
The more interesting thing on Windows would actually be COM, which is something like Java interfaces but for native code, that are optionally cross-process.
- rusk 4mo ago
  In my recollection COM became ActiveX which fell down the distributed objects hole along with CORBA because it embodied many of these fallacies.
  - inigyou 4mo ago
    COM still exists. That is like saying Java fell down the Spring framework rabbit hole. It did, but you can still use Java without using Spring.
    - rusk 4mo ago
      It still exists? Like Java still exists
      - inigyou 4mo ago
        It still exists and it's used by windows APIs, even recently designed ones