| Re: Is there a way to distinguish an auto-refresh from a manual page load? [message #177199 is a reply to message #177196] |
Sun, 26 February 2012 20:09   |
crankypuss
Messages: 147
Registered: March 2011
Karma:
|
Senior Member |
|
|
On 02/26/2012 11:44 AM, Peter H. Coffin wrote:
> On Sun, 26 Feb 2012 11:08:25 -0700, crankypuss wrote:
>
>> I've never been successful in digging around to find out how the few
>> web pages I've seen are able to update the page without constant
>> flickering and so on, it's my impression (*not* understanding, I lack
>> that) that http is a client/server protocol and that once a request
>> has been fulfilled the transaction is over. I'm curious, but not
>> compelled.
>>
>> On the other hand I have been somewhat successful in creating the same
>> appearance by using closely spaced refreshes, most browsers seem not
>> to clear the screen prior to rendering so if the next is mostly the
>> same as the last it appears to have been partially updated.
>>
>> I'm not sure what you mean by "web sockets", I've used the kind of
>> sockets provided by PHP but if you mean something else I've no clue
>> what that might be.
>
> javascript does not shut down just because the page is finished
> loading. The javascript makes a background request to a specialize "not
> generating a web page, just feeding data" script on the server, then
> updates its own document (that is, the rendered page) based on the new
> data it receives.
Pretty tough to implement when the user has chosen to disable js, but
then I assume that one of the items on the agenda of those in control is
to remove that choice from the idiot non-purchasing user's hands while
working toward stealing from him if he is unwilling to give.
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]