Imagine what happens if two svdrp connections both want to delete the
timer number 13. Most likely timer 13 + 14 will get deleted since you're
deleting not a timer number but an index in the list of all timers which
will change after the first delete ....
Lots of problems ..
As I've stated in a previous post, there is a rather simple
solution to this. Every SVDRP connection will have to issue an LSTT
command before it may add, modify or delete a timer. The timer list will
have a timestamp marking when the last modification was made. If an SVDRP
connection issues a timer modification command, but the list of timers was
in some way modified after this sessions last LSTT command, it will get
an error message, saying that the timers were modified in the meantime,
and that it should do another LSTT.
Which for sure will break a lot of applications anyway.