3 ms·
> Why does everybody use tcp ports instead of file sockets for local communication? In my experience it's because Windows and mac developers aren't aware of lo
by inetknght 4y ago
> Why does everybody use tcp ports instead of file sockets for local communication?
In my experience it's because Windows and mac developers aren't aware of local file sockets. Windows API, in particular, doesn't have a similar concept if I recall.
- duped 4y agoWindows has named pipes. MacOS has UDS and they're not terribly uncommon
- eptcyka 4y agoWindows also supports UDS now.
- sph 4y agoI've never seen the UDS acronym to refer to UNIX sockets. Just call them UNIX sockets.
- eptcyka 4y agoThey're called UNIX domain sockets. Just call them UDS.
- sph 4y agoOn the most popular UNIX-like operating system, Linux, there's are literally zero references to UDS to mean UNIX domain sockets. $ sudo mandb $ man -K UDS The point is that acronyms that are not context appropriate and/or very uncommon are quite annoying to come across. I guess it was worth saving a dozen bytes not to write the full thing in the first place.
- 10000truths 4y agoWindows 10 has support for UNIX sockets.
- nu11ptr 4y agoWow, interesting - I didn't know that. That is very cool... no more special handling for windows in cross platform handling then it sounds like (at least for UDS).
- origin_path 4y agoWindows added UNIX domain sockets in recent years. They work everywhere now.
- cpuguy83 4y agoDepending on what you need to do. Last I looked things like SCM_RIGHTS.