[pulseaudio-discuss] Client-server bad design

Lukas Polacek lukas at ksp.sk
Fri Mar 27 07:41:58 PDT 2009





On Mar 27, 2009, at 14:47, Colin Guthrie <gmane at colin.guthr.ie> wrote:

> 'Twas brillig, and Lukas Polacek at 27/03/09 08:51 did gyre and  
> gimble:
>> This may seem like a stupid play with the words, but this design  
>> flaw causes,
>> that you can't use PA over NAT without workarounds.
>
> PA works pretty much the same way that X works. X clients  
> (applications) connect to a server. Pulse clients (apps) connect to  
> a server.
>
> If I SSH from machine A to machine B and run an application, machine  
> B is the client and connects to machine A. There is no need for a  
> server to be running on B as it is just a client.
>
> The same is true of pulse apps. The only reason X works over NAT, is  
> that ssh is X aware and forwards the connections and sets the  
> DISPLAY variable correctly on your destination machine.
>
> If you want to make pulse work over NAT, you just have to make SSH
> pulse aware too, and make it set the PULSE_SERVER variable on the  
> destination machine.
>
> But your bandwidth will suffer.
>
> Col

Thanks for the answer. It makes sense.

Lukas



More information about the pulseaudio-discuss mailing list