|
| 1 | +A lower-quality library also encounters |
| 2 | +performance and memory issues, such as large |
| 3 | +documents with frustratingly long wait times for |
| 4 | +your users as well as complex documents that |
| 5 | +crash the viewer. This is often due to the absence |
| 6 | +of features such as PDF tiling, parallelization, |
| 7 | +and linearization that a more mature PDF SDK |
| 8 | +will incorporate. |
| 9 | +Some solutions (e.g., image servers) perform |
| 10 | +excellently when tested on a small number of |
| 11 | +documents and users but then inflict unexpected |
| 12 | +hidden costs when scaled up. When hundreds |
| 13 | +or thousands of users later view, mark up, comment |
| 14 | +on, and otherwise interact with (i.e.,scroll, |
| 15 | +pan, and zoom) documents, server resource and |
| 16 | +network data usage explodes. To maintain your |
| 17 | +desired UX, you have to pay higher fees or invest |
| 18 | +in more servers. |
| 19 | +The following types of documents have much |
| 20 | +more demanding rendering requirements: |
| 21 | +• CAD-based PDFs such as construction and |
| 22 | +engineering drawings with very large and |
| 23 | +complex designs. |
| 24 | +• Reports, textbooks, and marketing material |
| 25 | +using advanced PDF graphics such as shadings, |
| 26 | +gradients, soft masks, and patterns. |
| 27 | +• Geospatial maps with OCG layers that are |
| 28 | +switched off by default. |
| 29 | +• Pre-press documents which require an SDK |
| 30 | +with advanced color management features to |
| 31 | +print colors accurately. |
| 32 | +• High-speed accurate rendering (especially on |
| 33 | +native mobile apps and mobile browsers). |
| 34 | +• Context extraction of tables, text, etc. with |
| 35 | +document structure (e.g., text read order or |
| 36 | +table arrangement) in tact. |
| 37 | +To prevent crashes, slowness, and rendering |
| 38 | +issues from disrupting your UX, test functionality |
| 39 | +with the types of documents your users will work |
| 40 | +with. Also test a server-based solution at the |
| 41 | +anticipated load and usage. |
| 42 | +6 |
0 commit comments