Summary: | Please make READING a workbook thread safe | ||
---|---|---|---|
Product: | POI | Reporter: | m.kurz |
Component: | POI Overall | Assignee: | POI Developers List <dev> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | m.kurz |
Priority: | P2 | ||
Version: | 3.14-FINAL | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Attachments: | example |
Description
m.kurz
2016-06-03 20:04:05 UTC
I don't think there are any plans to do this. The sample exception that you list shows the types of problems that we would run into. Any lazily-initialized data-structure would be a potential case of errors. Sometimes the error message will be much harder to interpret or there even might be very strange incorrect behavior without any indication that multi-threading access is the culprit. Therefore I am closing this as WONTFIX for now. Even if someone would come up with some initial patches, I would vote against changing the official stance on multi-threading as such a guarantee would come with an additional maintenance burden that very likely no-one is willing to provide. Lastly, any such change likely has some performance impact on current single-threaded usages of the code, thus creating other problems for cases where large documents are processed already now. |