View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001378 | unreal | documentation | public | 2003-11-23 03:21 | 2003-11-26 00:26 |
| Reporter | CommodoreAttack | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | open | ||
| Product Version | 3.2-beta18 | ||||
| Summary | 0001378: Feature request for Primary and Secondary links on non-hub servers. | ||||
| Description | I would like to sugest that Unreal add the ability to have automatic primary and secondary links for all leaf servers. If a server is configured as a leaf, it would have multiple links instead of one. It would then have a priority on the links. The main link will always be used unless it goes down. In the event that the main link dies, the ircd would then attempt the secondary hub links after X number of reconnection attempts. When the main hub became avalible again for X period of time, it would auto reconnect to the normal hub. This is mainly in order to preserve the integrety of an IRC net in the event of a hub failure. | ||||
| 3rd party modules | |||||
|
|
Sorry, I accidentally posted this in the wrong catagory. This should have been in the ircd catagory. |
|
|
Sounds like redundant linking? |
|
|
I think this is just a very slight advantage over 2 link blocks. |
|
|
If it works the way I think, then wouldnt the server actually be linked to the network in more than one place, therefore leading to redundant information and excessive collision? And doesnt this also contravene the protocol? I agree with syzop here in that 2 link blocks are better... Hell... I think I just contradicted myself :P |
|
|
I am not talking about redundent links here...What I said was to have a backup link that the server will automatically try in the event the main link fails. Example. A server's link with the main hub fails. It will retry the main link for a set number of trys then will fall back on the secondary link block and connect to it. It could be done by just having the tag secondary; in the config and adding the code to the ircd. The point here is to keep a network online in the even to link failures without requireing a manual /connect to get a server to link back. Once the link is up again, the staff could easly use a /connect to get it back on the primary link. This is mostly a good feature for network stability. |
|
|
Rejected. Just use 2 link blocks with autoconnect. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2003-11-23 03:21 | CommodoreAttack | New Issue | |
| 2003-11-23 03:24 | CommodoreAttack | Note Added: 0004082 | |
| 2003-11-23 13:20 | cyberCloWn | Note Added: 0004083 | |
| 2003-11-23 16:08 | syzop | Note Added: 0004084 | |
| 2003-11-24 03:19 | w00t | Note Added: 0004086 | |
| 2003-11-26 00:02 | CommodoreAttack | Note Added: 0004125 | |
| 2003-11-26 00:26 | syzop | Status | new => closed |
| 2003-11-26 00:26 | syzop | Note Added: 0004126 |
