Re: Suggestions from a new GNATS/gnatsweb user

William M. (Mike) Miller wrote:
> 3. Although gnatsweb removes empty query fields in many of the
>    links it displays, the ones that go through get_pr_url do
>    not.  This affects, notably, the "view" and "edit" links in
>    each row of query output, so the extra baggage can add up,
>    especially for the result of an "advanced query", which will
>    typically have lots of empty fields.
>
>    (On a more global note, this URL is used in the return_url
>    field, which allows an automatic return to the query results
>    page after editing a PR on that page.  This mechanism is
>    really wasteful of bandwidth, adding many, many KB to each
>    query results page for all the return_url fields.  This
>    really ought to be implemented by using a cookie, not by
>    embedding the query in every link on the page!  If I get the
>    time, I'm going to look into changing this into using
>    cookies.)
>
> (snip)
Although there are lots of corner cases where this method won't have 
full effect (as you mention in later posts in this thread), it looks 
fairly safe and helps quite a bit to reduce url length. I have committed 
the patch. Thanks.

And yes, replacing the return_url by a cookie containing a tightly 
"optimized" return url should be investigated.

Yngve Svendsen
Gnatsweb maintainer