support Windows?

[razorfrost44]

From sockopt.cc

npm ERR! command failed
npm ERR! command C:\Windows\system32\cmd.exe /d /s /c node-gyp-build

error C1083: Cannot open include file: 'sys/socket.h': No such file or directory

[derhuerst]

Please provide more details about your environment: OS version, Cygwin installed?, etc.

However, I assume that Windows doesn't natively implement the UNIX sockets API, and that this is why you can't install the sockopt package as-is.

According to a StackOverflow discussion, Cygwin implements some of the sockets API, but I'm not sure if it will work.

[razorfrost44]

Win version 23H2. Cygwin not installed. Oh I apologize. I see you removed support for windows builds. I was attempting to use it set the 'socket' sizes with nodejs on windows and macOS. I was using it to hopefully apply the nodejs 'sockets' buffer sizes (high water mark) which are named pipes in windows. Thanks!

[derhuerst]

Win version 23H2. Cygwin not installed. Oh I apologize. I see you removed support for windows builds.

Let me know if you (or someone else) knows how to support Windows in a not-too-complex and maintainable manner.

I was attempting to use it set the 'socket' sizes with nodejs on windows and macOS. I was using it to hopefully apply the nodejs 'sockets' buffer sizes (high water mark) which are named pipes in windows. Thanks!

Note that the term "high water mark" (that the Node.js docs commonly refer to, e.g. here) is a property of a Node.js Stream and not the same as the SO_SNDBUF as mentioned in the node-sockopt readme! SO_SNDBUF determines how much the kernel buffers.

[razorfrost44]

I do know it is a part of the nodejs stream thanks =]

I had too many situations in my brain and was thinking this would work for both win and mac mistakenly. Because nodejs doesn't allow you to configure the "high water mark" when connecting only when setting up a server. So I am figuring out a way around that. I will test this out on mac thanks!

I would be happy to close this unless you want it to remain open just for the sake of if we can support this functionality on windows. I will be looking into it.

[derhuerst]

Because nodejs doesn't allow you to configure the "high water mark" when connecting only when setting up a server. So I am figuring out a way around that. I will test this out on mac thanks!

There are two places then where the Node.js Streams' high water marks can be configured: both on the server side and on the client side.

I would be happy to close this unless you want it to remain open just for the sake of if we can support this functionality on windows. I will be looking into it.

I'd like to keep this open.

[razorfrost44]

both on the server side and on the client side

Really? I am using the NodeJS Sockets to be specific and it only has high water mark in the server that I have seen. Is it possible to set the underlying stream directly in TypeScript do you happen to know?

PS: You are amazing! Thanks for the tips!

[derhuerst]

Is it possible to set the underlying stream directly in TypeScript do you happen to know?

http.ClientRequest inherits from http.OutgoingMessage, which in turn inherits from Stream, so you should theoretically be able to configure the high water mark. However, in practice I don't see any API to set a single stream's high water mark, only stream.setDefaultHighWaterMark(objectMode, value) to set it globally.