Random PA Deployment Idea

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I'll detail the package problems later. No time now.

> You can do this now, no problem. You need to have a look at the tunnel
> module. That module will give you a local sink that forwards everything sent
> to it to a remote PA instance. That way you can do local stream transfer and
> have it end up going remote.

I will go over the tunnel. I don't like that it requires configuration,
though. =)

> Each additional intermediate PA instance adds latency, which is really not
> ideal. Besides that, the per-user PA instances in your scenario don't do
> anything that the system instance couldn't do, so there's not much point in
> having them.

> What would make more sense IMHO, would be zeroconf detection of other PA
> instances *in the server* instead of (or perhaps in addition to) in the
> client libraries. That way, when one PA instance detects another on the
> network it could automatically create a tunnel sink which would allow
> dynamic stream transfer to the remote instance.

Except that this makes authentication which should rightly happen
between the client and the remote server harder. Creds have to make
their way through the local server somehow.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20061218/af16ed1a/attachment.pgp>


[Index of Archives]     [Linux Audio Users]     [AMD Graphics]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux