Okay, I'll keep things happening on the Database Server thread, as they currently are.
I plan to make time this week to finish my work on adding some new "states" for the Database Event Listener. Regards, Steve On Thursday, 15 March 2012 21:56:27 UTC+1, Thomas Mueller wrote: > > Hi, > > > The DatabaseEventListener notifications run on the database server > thread. > > Yes, I think that's fine. > > > A consequence is that an API user might inadvertently write code that > causes > > delays to the query. > > That's his problem. Maybe he actually wants to delay the query. > > > So I propose also making the calls > > to DatabaseEventListener.setProgress run using a dedicated Executor. > > No, I think that's not necessary. > > > Shall I make the notifications asynchronous? > > No, please not. If such a feature is required, the > DatabaseEventListener implementation could process this > asynchronously. Possibly DatabaseEventListener could be stacked. If > that ever is a problem. > > Regards, > Thomas > > -- You received this message because you are subscribed to the Google Groups "H2 Database" group. To view this discussion on the web visit https://groups.google.com/d/msg/h2-database/-/cjz-rQQOfPQJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/h2-database?hl=en.
