| Re: Is there a way to distinguish an auto-refresh from a manual page load? [message #177196 is a reply to message #177194] |
Sun, 26 February 2012 18:44   |
Peter H. Coffin
Messages: 245
Registered: September 2010
Karma:
|
Senior Member |
|
|
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.
--
For every subject you can think of there are at least 3 web sites.
The owners of these web sites know each other and at least one of
them hates at least one of the others.
-- mnlooney's view of Skif's Internet Theorem
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]