What exactly does the item type "+ item is a redundant server" mean in RFC 1436?
How does it work and what can I do with it?
0Fermenting Conkers /conkers/fermenting bigben.example 70
+Fermenting Conkers /conkers/fermenting bigben.example 7070 +Fermenting Conkers fermenting-conkers bigben.example 70
+Fermenting Conkers /conkers/fermenting greatpaul.example 70
The information applies to a duplicated server. The information
contained within is a duplicate of the primary server. The primary
server is defined as the last DirEntity that is has a non-plus
"Type" field. The client should use the transaction as defined by
the primary server Type field.
'+' items add alternative locations to the previous (non-'+') item.
For example:
0Fermenting Conkers /conkers/fermenting bigben.example 70
+Fermenting Conkers /conkers/fermenting bigben.example 7070 +Fermenting Conkers fermenting-conkers bigben.example 70
+Fermenting Conkers /conkers/fermenting greatpaul.example 70
Primary use is if host bigben.example is down, a connection may be
attempted to alternate hosts (hence 'redundancy').
From tidbits I've read they may have been used for load-balancing too.
I'm unsure if having differing label has ever had an effect - the
obvious is an alternate title - if someone else could shed light
they'd have my gratitude.
| Sysop: | Amessyroom |
|---|---|
| Location: | Fayetteville, NC |
| Users: | 76 |
| Nodes: | 6 (0 / 6) |
| Uptime: | 54:19:59 |
| Calls: | 1,265 |
| Calls today: | 1 |
| Files: | 1,362 |
| D/L today: |
3 files (2,684K bytes) |
| Messages: | 285,563 |