izaya/OC-Copper
1
0
Fork 0
mirror of https://github.com/XeonSquared/OC-Copper.git synced 2024-11-23 09:58:06 +11:00
Code Issues Releases Wiki Activity

Broadcast Address support.

Browse Source
This commit is contained in:
gamemanj 2017-03-18 16:12:31 +00:00
parent d63ba8db06
commit b5013044f6
2 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
culib.lua
View File

@ -132,7 +132,9 @@ return function (hostname, transmit, onReceive, time)
return return
end end
if fnam ~= "*" then
lastKnownReceiver[fnam] = {node, t + tuningExpectContinue} lastKnownReceiver[fnam] = {node, t + tuningExpectContinue}
end
onReceive(fnam, tnam, message) onReceive(fnam, tnam, message)
if culib.hostname == tnam then return end if culib.hostname == tnam then return end

5
protocol.0
View File

@ -41,9 +41,10 @@ Should a situation be dire enough,
--- The Broadcast Address --- The Broadcast Address
The Broadcast Address is a possible feature which may or may not be actually used. The Broadcast Address is a possible feature which may or may not be actually used.
For now it is not implemented. It has been implemented with forward compatibility by simply ensuring that "*" is never put into the
routing cache (so it's always broadcast).
The idea is that if a name is directly equal to "*", it should be broadcast around the local network. The idea is that if a name is directly equal to "*", it should be broadcast around the local network.
Notably, it is completely incompatible with reliability mechanisms, Notably, it is completely incompatible with reliability mechanisms for probably obvious reasons,
but can still be used in networks running the Reliability Layer via the 'unreliable' escape-hatch. but can still be used in networks running the Reliability Layer via the 'unreliable' escape-hatch.
Hierarchial gateways do not need modification on the from-child rules Hierarchial gateways do not need modification on the from-child rules