connect to pa server through TCP socket

[smiccoli]

I've digged a bit in the docs, other issues (including #6) and code and I couldnt figure out how to address my issue.

Depending on the environment, I may need to connect to the PA server via unix socket or tcp socket.

For the former I managed by just passing the path, such as /mnt/wslg/PulseServer but tcp would not work with either tcp:<domain>:<port> or just <domain>:<port> or even <domain>

Is there any way to pass a tcp connection path? alternatively, Im fine with creating the socket manually and then passing it, but this is also not viable judging from the code, right?

[janakj]

Hi @smiccoli,

Pulseaudio.js internally calls net.createConnection to create the connection to the PulseAudio server, passing the third PulseAudio constructor argument (sockPath) to it. The type annotations require the corresponding argument to be a string, which will be interpreted by net.createConnection as a path to a UNIX domain socket.

Since Pulseaudio.js only transparently passes the argument to net.createConnection and does nothing else with it, you can try to disregard the type annotation and pass an object to the constructor instead:

const client = new PulseAudio(undefined, undefined, { host: "localhost", port: 1234 } as any);

An object argument should select this variant of net.createConnection.

I have not tested this. Please let me know if you get it to work. If it works, I would welcome a PR to add official support for TCP connections to the pulseaudio.js library!

Jan

[smiccoli]

ah, you are totally right! I just tested it and it works like a charm with both TCP and unix.
That's great news as it was the only thing blocking me from migrating.

Ill try to submit a PR in the next few days as soon as i find a slot