W3C home > Mailing lists > Public > www-jigsaw@w3.org > November to December 1996

RE: AutoStarting Resource (was Request for feature: Logger.sync())

From: Alexandre Rafalovitch <alex@access.com.au>
Date: Fri, 15 Nov 1996 14:25:43 +1000
Message-Id: <v03007802aeb19e728ba4@[203.18.229.116]>
To: www-jigsaw@w3.org
>Alexandre Rafalovitch writes:
> > At 9:03 PM +1000 12/11/96, Anselm Baird_Smith wrote:
> > I assume you want to use Timer entry to do checkpoint every N seconds.
> > Question is, how are you going to put Timer entry in the first place. If
> > you want to hardcode it, don't!
>
>Well, the problem with the httpd timer object, is that it's already a
>bottleneck (and as commiting changes might take long time, you really
>want a separate thread to run the code)
>

You mean it is a bottleneck because it is used for client timeouts? Would
establishing a second timer object (system vs client timers) solve the
situation?

 BTW, there should be some security on who can put what on Timer. Maybe
making timer resource package protected (default protection) would do the
trick?

Then the second timer would be accessable through the public function and
can have less priority as well as maybe a bit tougher securityManager
protection.

Regards,
  Alex.

alex@access.com.au
Received on Thursday, 14 November 1996 22:24:28 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:25 GMT