W3C home > Mailing lists > Public > public-html@w3.org > February 2008

server's initiative

From: Dmitry Turin <html60@narod.ru>
Date: Tue, 5 Feb 2008 12:59:42 +0200
Message-ID: <196104344796.20080205125942@narod.ru>
To: public-html@w3.org

Good day,

If browser does not close communication after downloading of page,
it can get xml-elements (after closing tag </html>),
sent by server at arbitrary moment of time. These xml-elements could
*) change position of html-elements <obj   id= coord= >
*) change style                     <obj   id= newstyle= >
*) pronounce text                   <say   data="pronounce this">
*) download and play sound file     <sound src="site.com/filename.mpg">
*) add new html-elements            <tag_except_4_above parentId= afterId= >
This allow to turn browser into control desk (control panel),
displaying state of some process (on server side).


I'd like to know your opinion, is it enough to inform browser
to not close communication by
  <head>   <meta name=connection content=prolong>   </head>
Server, keeping this page, never close communication by own
initiative, and can recognize, that communication is not closed
by browser.

Or it's necessary to send some information to server, like
  <formdata>   <prolong doc=785>   </formdata>
on base of
  <head>   <meta name=register content=785>   </head>


As it seems, nothing additions for HTTP is not needed.




Dmitry Turin
HTML6     (6. 5.2)  http://html60.euro.ru
SQL5      (5.11.0)  http://sql50.euro.ru
Unicode7  (7. 2.1)  http://unicode70.euro.ru
Computer2 (2. 0.2)  http://computer20.euro.ru
Received on Tuesday, 5 February 2008 10:57:44 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:38:52 UTC