4 ms·
> unmounting-aware APIs Does that mean libraries need to be rewritten to support it? In my experience, important IO-driven libraries like database access/ORMs
by bpicolo 8y ago
> unmounting-aware APIs
Does that mean libraries need to be rewritten to support it? In my experience, important IO-driven libraries like database access/ORMs tend to be extremely poorly supported for non-language-native concurrency strategies, or even concurrency strategies added late in a language's lifecycle.
- BenoitP 8y ago> Does that mean libraries need to be rewritten to support it? Yup. Here are the list of supported libraries [1]. > even concurrency strategies added late in a language's lifecycle Quasar code uses a regular Java Exception as a trick to stop execution and unmount, to sort of piggyback on the language features. Fibers do also implement the Thread interface; I think what you pointed at was indeed a concern of the author. I don't know how the Loom initiative look like. If you want to see how a library is adapted, here is JDBC [2]. [1] http://docs.paralleluniverse.co/comsat/#getting-started http://docs.paralleluniverse.co/comsat/#getting-started [2] https://github.com/puniverse/comsat/tree/master/comsat-jdbc/src/main/java/co/paralleluniverse/fibers/jdbc https://github.com/puniverse/comsat/tree/master/comsat-jdbc/...