[ https://issues.apache.org/jira/browse/PDFBOX-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14979839#comment-14979839 ]
John Hewson commented on PDFBOX-3001: ------------------------------------- I agree, writing to writing to /tmp is probably not that useful, especially as on some systems each process is siloed into its own tmp subdir, which would prevent the cache from ever being re-loaded. Containers are doomed anyway, as the entire point is that they're ephemeral so the cache won't be persisted between runs. {quote} As an end-user, I'd prefer a default `$HOME/.something`, configurable via system property. {quote} Yes. > FileSystemFontProvider cache instability > ---------------------------------------- > > Key: PDFBOX-3001 > URL: https://issues.apache.org/jira/browse/PDFBOX-3001 > Project: PDFBox > Issue Type: Bug > Affects Versions: 2.0.0 > Reporter: John Hewson > Assignee: John Hewson > Priority: Blocker > Fix For: 2.0.0 > > Attachments: md5.diff, patch, patch > > > FileSystemFontProvider uses Java's Preferences API to cache font metadata, > however it doesn't seem to work out of the box on Windows (due to file > permissions) and one user on the mailing list has complained that on Linux > file paths with more than 80 characters can't be handed. Serializable is also > slow. > It looks like Preferences wasn't a good choice here. We're going to need to > roll our own cache file format and save it somewhere we have write access to. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@pdfbox.apache.org For additional commands, e-mail: dev-h...@pdfbox.apache.org