Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
rename addMembershipCertificate to more security-descriptive validateAndAddMembershipCertificate, give it a return value, and drop unused force parameter.
|
|
well supported or easily configurable anyway) -- this is really left over from the old collaborative multicast propagation algorithm. New algorithm (in for a while) has been sender-side replication in which sender "pays" all bandwidth, which intrinsically limits multicast.
|
|
optimization to avoid repeated calls to _allMulticastGroups().
|
|
|
|
for consistency.
|
|
core, other bug fixes.
|
|
|
|
|
|
|
|
|
|
behind me.
|
|
|
|
|
|
|
|
|
|
out, redo COM serialization, etc.
|
|
|
|
|
|
|
|
|
|
reinstate legacy support.
|
|
of certificates of membership.
|
|
|
|
|
|
|
|
not added backward compatibility support for relaying of multicasts to 0.9.X clients yet but that will be easy. Will test with heterogenous 1.0.0 clients only first.
|
|
Network to remove redundant code and bug-proneness, more work on IncomingPacket...
|
|
|
|
|
|
|
|
|
|
controller but different code. More descriptive though.
|
|
little more consistent about using _ to denote private member variables.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
network now doesn't leave networks in limbo.
|
|
also fix GitHub issue #90
|
|
Otherwise a dead active bridge might kill multicast for us.
|
|
|
|
bridge list, not three mode types. Also change isOpen to isPublic for terminology consistency.
|
|
|
|
|
|
|