W3C home > Mailing lists > Public > www-html@w3.org > April 2000

RE: Add timeouts for security to HTML

From: Dave J Woolley <DJW@bts.co.uk>
Date: Thu, 20 Apr 2000 12:26:49 +0100
Message-ID: <81E4A2BC03CED111845100104B62AFB58245D2@stagecoach.bts.co.uk>
To: "'www-html@w3.org'" <www-html@w3.org>
> From:	Sameer Ajmani [SMTP:ajmani@chord.lcs.mit.edu]
> 
> I suggest an HTML tag that specifies when an object should "timeout":
> the browser can "gray out" the classified object when the specified
	[DJW:]  
	"gray out" has no meaning in a structural markup 
	context.  How do you grey out a text only or voice
	synthesized display?  Even in GUI browsers, greyed
	out material is normally perfectly readable.

	What does "object" mean in this context?

> amount of time has passed since the page was loaded from the server.
> Alternately, the server could specify and expiration date for the
> object.  The browser should also gray out classified objects on pages in
> cache.
	[DJW:]  
	To the extent that an object equates to a page, this
	is already catered for within HTTP, which is the
	right place to handle page (or object element) level
	controls.

	I'd suggest that URL level is the only realistic level
	at which to apply such controls and therefore it is a
	question of how the browser handles existing cache
	control meta data from the HTTP protocol.  In particular,
	HTML level controls cannot do anything about PDF, flash,
	etc. content.

	In any case, this is not real security as one can easily
	substitute a browser that doesn't enforce the policy.
Received on Thursday, 20 April 2000 07:32:32 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 March 2012 18:15:43 GMT