T134205: Options for browser-based server-side PDF generation has several remarks like Render performance: Complex pages can generally be rendered in a few seconds, which avoids the need for custom queueing and caching solutions. That's for single pages; we might want to reevaluate it for books. (Example of a largish book: A Brief Guide to the Solar System is 332 pages vs. Obama's 30 in the quoted task, and takes minutes in OCG.)
Two questions come up:
- is it OK UX-wise to force the user to keep a download open so long?
- can there be problems from open connection count spikes exhausting the pool, or something like that?