Groups | Search | Server Info | Keyboard shortcuts | Login | Register

Groups > comp.infosystems.gopher > #649

Re: RFC1436 "+ item is a redundant server"

Show all headers | View raw

On Thu, 3 Mar 2022, Gopher Space <info@gopherspace.de> wrote:
> 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?

'+' 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.

RFC 1436 states in the appendix:
> 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.

Not too helpful.

(I'm aware this is an old post - I've seen it questioned a few times &
am taking the oppurtunity to educate others.)

Back to comp.infosystems.gopher | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

RFC1436  "+ item is a redundant server" Gopher Space <info@gopherspace.de> - 2022-03-03 06:40 -0800
  Re: RFC1436  "+ item is a redundant server" Olive S <oliversimmo@gmail.com> - 2024-01-12 11:53 +0000
    Re: RFC1436  "+ item is a redundant server" Olive S <oliversimmo@gmail.com> - 2024-01-12 12:15 +0000

csiph-web