[vdr] Re: How to kill an svdrp connection from vdr ?

[Philip Lawatsch <philip@lawatsch.at>]

Udo Richter wrote:
> Klaus Schmidinger wrote:
>
> > DELR depends on a previous LSTR (for the recording number).
> > DELT, MODT and UPDT depend on a previous LSTT (for the timer number).
> > MODC depends on a previous LSTC (for the channel number).
> > HITKs from different connections could lead to complete confusion.
> >
> > So it just isn't that simple...
>
> What about adding LOCK and ULCK commands to request exclusiveness 
> whenever needed, and allow concurrent access otherwise?
>
> LOCK could wait for a timeout, and if someone is blocking in exclusive 
> mode, fail. After LOCK succeeds, this connection has exclusive access to 
>  modification commands until ULCK or disconnect.
>
> To keep compatibility, all list and modification commands need to 
> auto-lock of course. Maybe just keep compatibility mode until first use 
> of LOCK or ULCK.
> Shouldnt be too difficult to implement and should not break too much 
> compatibility.
This would require every single application using svdrp to be rewritten.
That breaks a lot imo :)

And, the problem is that a single command like list cannot be 
auto-locked. Since after a list command there might be a modification or 
not.

Imho the best idea would be to turn away from numbers and use ids.

kind regards Philip