[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Yet another change in terminology: request-routing
- To: <firstname.lastname@example.org>
- Subject: Yet another change in terminology: request-routing
- From: "Mark Day" <email@example.com>
- Date: Fri, 17 Nov 2000 11:37:16 -0500
- Delivery-date: Fri, 17 Nov 2000 08:37:34 -0800
- Envelope-to: firstname.lastname@example.org
I'm a little behind in recording this, but I don't want for people to be
surprised by this change in the documents.
We had a design team conference call on Tuesday at which a number of people
expressed dissatisfaction with the term "mapping". We went through the
following collection of alternatives:
We took a straw poll of the people on the call. There were only two
candidates that people actually nominated for being voted on:
"request-routing" got 4 votes, "delegating" got 2 votes, and 3 people
thought that either was equally (un)palatable. This vote is of course
indicative, not decisive: "request-routing" has not "won", but we will use
it for now until/unless a rough consensus develops around a different term.
We agreed that it is not acceptable to drop the "request-" prefix, i.e. this
is never referred to as "routing" and the entities doing it are never
referred to as "routers".
Coherent arguments for other terms are still welcome, both on the list and
at the BOF, but please make sure that any such argument consists of
something more than "I like foo" or "I don't like request-routing." We need
some reasoning behind what you like or dislike, such that you think others
might be convinced.