From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-www(at)postgresql(dot)org" <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: Excessive # usage in URLs |
Date: | 2015-10-23 15:26:43 |
Message-ID: | 20151023152643.GZ3391@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
Stephen Frost wrote:
> * Magnus Hagander (magnus(at)hagander(dot)net) wrote:
> > The point of the # is that you actually want to point to that specific
> > message in the thread. If you just pick the first message in the thread we
> > could exclude it, but how else would you link to a specific message?
>
> The request isn't to remove the "#" ability for the flat view entirely,
> it'd just be nice if the site didn't redirect to having the "#" when the
> message-id after the "#" is the same as the one before the "#" (iow,
> it's the first message).
Here's another idea. Right now the <A NAME="tag"> tag is the
message-id, but since messages are added consecutively to a thread, we
could just assign each of them a number, so that to link the second
message in a thread we could do this
http://www.postgresql.org/message-id/flat/20151023125233(dot)GQ3685(at)tamriel(dot)snowman(dot)net#2
We could do this in addition to the message-id-based NAME tag.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2015-10-23 15:28:12 | Re: Excessive # usage in URLs |
Previous Message | Stephen Frost | 2015-10-23 15:23:55 | Re: Excessive # usage in URLs |