Hi, For (table-level-) locking, H2 doesn't use java.util.concurrent because this doesn't support lock upgrade.
I guess more and more of java.util.concurrent will be used where it makes sense, but currently there is little need for it. Areas where it would help are (probably) seqence generation for in-memory databases. About the background writer thread: One additional thread per database is not that heavy, except if you have many databases open concurrently (do you? if yes why?). Many databases use a separate process for this. 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.
