| Re: Is there a way to distinguish an auto-refresh from a manual page load? [message #177200 is a reply to message #177198] |
Sun, 26 February 2012 21:12   |
The Natural Philosoph
Messages: 993
Registered: September 2010
Karma:
|
Senior Member |
|
|
crankypuss wrote:
> On 02/26/2012 11:40 AM, J.O. Aho wrote:
>>
>> Web sockets has been introduced with html 5 (and there are a few
>> diffe3rent standards too), which allows the server to push content to
>> the browser instead of using ajax which pulls information from the
>> server.
>
> I will studiously avoid this, then; the redeeming graces of html are few
> enough already... I really don't care a whit about conforming to the
> expectations of html conformance freaks, as far as I'm concerned a
> browser is simply a remote rendering device
Well' that's your view. I see it as a fairly ubiquitous fairly thick
client for wep Apps. I am just as interested in it in intranets as on
the internet.
websockets and javascript are part of that - and in an intranet
situation you can insist on a single browser.
and document source format
> is relevant only insofar that it determines semantics as related to the
> remote rendering device. It seems impossible to be a purist and an
> html-purist at the same time. Push is like Jehovah's Witnesses banging
> on the door and should similarly be shot or hanged or simply beaten and
> sent on its way, whichever is more convenient.
Websockets are really nothing more than a persistent two way comms
channel. I'd guess only of relevance with Javashite (TM) as well.
BUT its a better use of bandwidth to push changes down the channel when
they happen, rather than constantly polL.
It might save my bandwidth when my wife leaves the weather radar live
on overnight...
|
|
|
|
Calendar
Search
Help
Members
Register
Login
Home
]