summaryrefslogtreecommitdiff
path: root/HISTORY
diff options
context:
space:
mode:
authorKlaus Schmidinger <vdr@tvdr.de>2015-05-22 13:44:43 +0200
committerKlaus Schmidinger <vdr@tvdr.de>2015-05-22 13:44:43 +0200
commitc3b03475569b7a59186b5a30c09325a4b3408cbe (patch)
tree38fa011cc6c2ca151a6233d4ec8308288cf11be1 /HISTORY
parent2b9e988dd563d66a8a341a359d17c51032cbca40 (diff)
downloadvdr-c3b03475569b7a59186b5a30c09325a4b3408cbe.tar.gz
vdr-c3b03475569b7a59186b5a30c09325a4b3408cbe.tar.bz2
Implemented SVDRP peering
Diffstat (limited to 'HISTORY')
-rw-r--r--HISTORY24
1 files changed, 19 insertions, 5 deletions
diff --git a/HISTORY b/HISTORY
index 20a6b682..e65f99d7 100644
--- a/HISTORY
+++ b/HISTORY
@@ -8652,8 +8652,22 @@ Video Disk Recorder Revision History
"Setup/Miscellaneous/SVDRP timeout (s)").
- The SVDRP log messages have been unified and now always contain the IP and port
number of the remote host.
-- SVDRP connections are now handled in a separate thread, which makes them more
- responsive. Note that there is only one thread that handles all concurrent SVDRP
- connections. That way each SVDRP command is guaranteed to be processed separately,
- without interfering with any other SVDRP commands that might be issued at the same
- time.
+- SVDRP connections are now handled in a separate "SVDRP server handler" thread,
+ which makes them more responsive. Note that there is only one thread that handles
+ all concurrent SVDRP connections. That way each SVDRP command is guaranteed to be
+ processed separately, without interfering with any other SVDRP commands that might
+ be issued at the same time. Plugins that implement SVDRP commands may need to take
+ care of proper locking if the commands access global data.
+- VDR now sends out a broadcast to port 6419/udp, which was assigned to 'svdrp-disc'
+ by the IANA. VDRs listening on that port will automatically initiate an SVDRP
+ connection to the broadcasting VDR, and in turn send out a broadcast to make
+ other VDRs connect to them. That way all VDRs within the local network will
+ have permanent "peer-to-peer" SVDRP connections between each other. The
+ configuration in the svdrphosts.conf file is taken into account when considering
+ whether or not to respond to an SVDRP discover broadcast.
+- The new SVDRP command PING is used by automatically established peer-to-peer
+ connections to keep them alive.
+- The new function GetSVDRPServerNames() can be used to get a list of all VDRs
+ this VDR is connected to via SVDRP.
+- The new class cSVDRPCommand can be used to execute an SVDRP command on one of
+ the servers this VDR is connected to, and retrieve the result.