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 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.
