Олег, et al.,
Yes, I thought about that (It would work even better if you replace /bin/cp
with /bin/ln:), but still, wouldn't a solution with one plugin work better,
namely, I've noticed that the start-up latency of VDR depends largely on a
number of loaded plugins.
Another solution that works, but still is unacceptable (to me), is to setup
another client in the first server that uses the second server (and so on).
In any case, for both solutions, channel switch time for a large number of
servers (say 10) will be much larger than ideal, since every server would
be queried serially. Doing it with just one client in parallel for every
configured server would be much more scalable I think...
Thanks for reply!
oleg roitburd wrote:
> 2008/1/14, Pjotr Kourzanov <[EMAIL PROTECTED]>:
>> Is there a patch for allowing streamdev-client to connect (using VTP) to
>> multiple streamdev-server's? Current code AFAIK only handles one IP for the
>> VTP server. What I actually want is to have streamdev-client support for
>> querying a list of servers (in some order) for a given channel, and then
>> connecting to a suitable one if several were found.
> it's easy. You don't need any patch ;-)
> Small translation
> Copy a libvdr-streamdev-client.so.$(APIVERSION) to
> libvdr-streamdev-client2.so.$(APIVERSION). Start a vdr with both
> clients, and define for each client a IP of server.
> vdr mailing list
vdr mailing list