On 05/24/18, Blue White pondered and said...
Moderated echos and better dupe prevention. Probably other benef
too. A message does not echo out to the other subscribed nodes un reaches the echo host for that echo. That is if I understand it correctly.
If that's the case it still seems to me to be a slightly weaker way
to run things. In fsxNet all the HUBs are fully meshed so although
dupes are caused at three HUBs each time something is posted by (lets
say) a node in NET 1, the other NETs have a far better chance of
getting the messages with the other three HUBs also sharing the same traffic between them.
I guess it really depends on your priorities, and how you rate fault tolerance. I don't know about GTPower, but in my own system if the hub rolls over then it's pretty catastrophic. If the node hosting an echo
area disappears, then so does the echo area, so yeah, not very fault tolerant -- but it's only been 4 days of thinking / implementing :)
FSXnet is better equipped to handle a hub failure as you say, but if one hub goes out, then a third of the network does too (assuming there are 3 hubs, not counting the frontdoor one).
So ultimately, you need all the nodes to be hubs, and all mesh together
to be fully fault tolerant, I guess that's kind of what you were talking about the other day with p2p networking.
However, it is my understanding that in this scenario, all nodes need to communicate all traffic to all other nodes else there is a chance for messages not to turn up?
If that's the case it still seems to me to be a slightly weaker way to
run things. In fsxNet all the HUBs are fully meshed so although dupes
If that's the case it still seems to me to be a slightly weaker w
run things. In fsxNet all the HUBs are fully meshed so although d
Not if you like moderated echos.
What exactly do you mean by moderated echos? Are messages themselves moderated and approved before going out on the area, or just who can connect to the area itself?
It all sounds a bit heavy to me... and given todays climate of nodes
opting for multiple feeds of the same echoarea .. the idea of locking
out someone via a feed cut seems largely nonsensical.
apam wrote to Avon on 05-28-18 14:23 <=-
It all sounds a bit heavy to me... and given todays climate of nodes
opting for multiple feeds of the same echoarea .. the idea of locking
out someone via a feed cut seems largely nonsensical.
Perhaps, but say someone wanted an area for just them and their
friends, they could whitelist only their friends nodes. Assuming they
kept their area available to only a select group on the BBSes,
otherwise anyone could post by connecting to their BBS.
Quoting apam to Blue White <=-
What exactly do you mean by moderated echos? Are messages themselves moderated and approved before going out on the area, or just who can
What exactly do you mean by moderated echos? Are messages themselves moderated and approved before going out on the area, or just who can connect to the area itself?
I've just done some work to hopefully do the latter, so that nodes that can connect to your area can be blacklisted or whitelisted. As for a moderator approving every post, it could be done I suppose, but seems
like a lot of work.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 537 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 140:42:43 |
| Calls: | 10,249 |
| Calls today: | 1 |
| Files: | 13,981 |
| Messages: | 6,407,573 |