I thought so, but couldn't remember it being discussed, my tunnel vision no doubt.
> -----Original Message----- > From: Peter M. Goldstein [mailto:[EMAIL PROTECTED]] > Sent: 26 September 2002 22:32 > To: 'James Developers List' > Subject: RE: Release Plan > > > > Danny, > > > > 2) Change code so that it doesn't use the TimeScheduler in the > assorted > > > server blocks (excluding the newly introduced FetchPOP) > > > > Sorry, slightly off the topic of this thread, whats wrong with > > TimeScheduler, and why is it OK for fetchpop, have I missed something? > > TimeScheduler is not designed to be used as it is being used by the > assorted Handlers. In each of the Handlers, it's being used as a > centralized generic timeout tool. This has led to observed memory, > robustness, and throughput problems (see archives for details) largely > because of the massive number of short lived tasks being managed by the > TimeScheduler. As FetchPOP uses it as it was intended to be used - as a > tool to execute tasks at scheduled intervals - there's no problem there. > > --Peter > > > > > > -- > To unsubscribe, e-mail: > <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: > <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
