Re: [TC4] ResourcesBase.setCheckInterval() (not a) bug

2000-11-16 Thread Boyd Waters
Boyd Waters wrote: > > [...this un-lurking is getting habit-forming...] > > "Craig R. McClanahan" wrote: > > > What would you think about using a JNDI DirContext as a representation of the > > resources available to a web application? > > Craig: > > I think that the *option* for Catalina to

Re: [TC4] ResourcesBase.setCheckInterval() (not a) bug

2000-11-16 Thread Craig R. McClanahan
Remy Maucherat wrote: > > > BTW: I really like the resources package! I can think of several useful > > > implementations that I'd like to use, like one for CVS, or one for > JavaMail, > > > or ... lots more. > > > > I like the Resources abstraction as well. Before we go whole hog at > creatin

Re: [TC4] ResourcesBase.setCheckInterval() (not a) bug

2000-11-16 Thread Boyd Waters
[...this un-lurking is getting habit-forming...] "Craig R. McClanahan" wrote: > What would you think about using a JNDI DirContext as a representation of the > resources available to a web application? The idea would be to use directory > entry attributes for the commonly used information like

Re: [TC4] ResourcesBase.setCheckInterval() (not a) bug

2000-11-16 Thread Remy Maucherat
> > BTW: I really like the resources package! I can think of several useful > > implementations that I'd like to use, like one for CVS, or one for JavaMail, > > or ... lots more. > > I like the Resources abstraction as well. Before we go whole hog at creating new > implementations, though, I'd

Re: [TC4] ResourcesBase.setCheckInterval() (not a) bug

2000-11-16 Thread Craig R. McClanahan
Jason Brittain wrote: > > BTW: I really like the resources package! I can think of several useful > implementations that I'd like to use, like one for CVS, or one for JavaMail, > or ... lots more. I like the Resources abstraction as well. Before we go whole hog at creating new implementations

Re: [TC4] ResourcesBase.setCheckInterval() (not a) bug

2000-11-16 Thread Jason Brittain
Hi Remy. Oops, yes, you're right about this (of course). I misunderstood the use of the "started" variable to mean whether or not the background thread was already started, instead of whether the component's lifecycle had started. Sorry. BTW: I really like the resources package! I can think