Product Ideas

As a Prizmdoc user, I would like the space efficiency and creation time of Viewing Packages to be improved.

I am currently unable to utilize Viewing Packages in my application because they take up too much space on the disk, and also take a very long time to generate.

A test with a 540 page .docx file of size 584 KB produced a 568 MB viewing package consisting of 7563 different files. The package also took 16 minutes to create.

In order for me to be able to use Viewing Packages, I would like their space efficiency and creation time to be improved. I would also like to be able to specify what kind of svg content will be generated in the viewing package (svg, svgb, svga).

  • Guest
  • Sep 13 2019
  • Shipped
  • Attach files
  • Mark Fears commented
    13 Apr 09:18pm

    The optimization of viewing packages has been addressed in PrizmDoc Viewer version 13.22 with two new features which called Hybrid Viewing Option and PDF Viewing Packages.

    PrizmDoc Hybrid Viewing Feature. This feature can reduce server load and enable more concurrent users per server. For more information, see the PrizmDoc Hybrid Viewing Feature topic. This feature is only available through metered licensing.

    As part of the Hybrid Viewing feature, you can now create Viewing Packages that contain only PDF content and necessary metadata to improve their performance by making them smaller and faster to generate. This feature requires licensing PrizmDoc Application Services (PAS) with a metered license. For more information, see the PDF-only Viewing Packages topic.

  • Vishrut Goyal commented
    17 Sep, 2019 06:36am

    Viewing package is one thing. We see that Viewing Session also creates both SVGB and SVGA formats in PrizmDoc server cache. Regarding this Accusoft Support says the following 

    Some versions of Internet Explorer 11 and earlier version of Edge would render garble if provided SVGB. As such, we used to detect those browsers and provide them SVGA. We do not do that anymore. Since around version 13.3 we provide all browsers SVGB, and most recently we made it so the browser gracefully falls back to SVGA when SVGB fails to render correctly.

     

    Our take on this is this

    Since Veritas is not interested in running PrizmDoc Viewer with IE and older versions of Edge , it does not make sense for us to generate SVGA format as part of Viewing session; it just unnecessarily consumes CPU and disk space. SVGA file should be generated by the PrizmDoc server only if (in rare case) Viewer is not able to render SVGB format correctly and explicitly sends request for SVGA format.

    Regards,

    Vishrut

     

  • +2