On Wed, 15 Aug 2001, Berin Loritsch wrote:
> Hopefully the framework will be generic enough for all that. My first concern
> is having a foundation that can handle alot of what Cocoon code does manually
> now. Its premise is we are monitoring things that change content. I.e. if
> the content of a resource has changed since time X.
Time should be optional, I beleive. It would be nice to have it, sure.
> All specific types of resources extend the Resource or StreamResource abstract
> classes.
Can we have an interface that bridges between the Monitor and the
monitored objects? I think the methods in it could be as simple as
stop()
start()
restart()
close()
Well, it depends on the monitored objects; in the case of threads, you
might not need close(). This could be useful in JDBC connections, though.
In stopping threads, you might need to interrupt them, I believe. My
current problem is how to stop (interrupt) delivery threads so that when
they have stopped, the database resources are returned to the pool. It
might need more than just interrupting the threads, I think; somekind of
message that tells what the threads should do when the interrupt comes
would be needed.
Oki
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
