Re: Processed: Re: bug#19717: 24.4.50; printing.el still uses ps-eval-switch

[Chad Brown <yandros@gmail.com>]

[-- Attachment #1: Type: text/plain, Size: 1798 bytes --]


> On 24 May 2016, at 10:25, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> From: Paul Eggert <eggert@cs.ucla.edu>
>> Date: Tue, 24 May 2016 09:47:35 -0700
>> Cc: rgm@gnu.org, emacs-devel@gnu.org
>> 
>> On 05/24/2016 08:59 AM, Eli Zaretskii wrote:
>>> I have hard time believing this is a browser issue
>> 
>> I don't. There are different kinds of refreshes, and it's possible that 
>> a partial refresh won't give you a new page at the same time that a full 
>> refresh would.
> 
> That makes no sense at all.  It's the same browser and the same Web
> page.  How can the browser know to refresh it in one case, but not in
> the other?

Because the refresh button doesn’t ask the web server for a new copy of the page; it instead asks the local cache to check and see if it thinks a new copy of the web page is needed. There are many circumstances where the local cache controller can ask the web server and get back what is effectively the wrong answer. C-F5 is a standard command that tells the web browser to have the local cache get a new copy of the page, without asking the web server if it can use the cached copy instead. In practice, this sort of thing happens in certain corners often enough that many people have developed the habit of always using the reload-dammit command when they’re sure they want a fresh page (see Kaushal Modi’s message, for example).

Debbugs could be changed to always give out a new copy of the page, with the concomitant increase in load you might expect from always bypassing the cache. It could presumably be changed to never give out the wrong answer, but (if this is what is happening in this case — it’s hard to tell without someone trying) that depends on specific effort being put into debbugs.

I hope that helps.
~Chad


[-- Attachment #2: Type: text/html, Size: 5080 bytes --]