Customer 001-00-017744 is interested in a PrizmDoc configuration option to not serve large files. They would like for this to be a configurable size. This will allow them to not overload weaker devices in addition to providing the appropriate message to the end user who can expect a longer than usual wait.
A weighty attachment will be slow on mobile devices. They just want to enforce a file size constraint in order to deal with large (> 100MB) files. This can be implemented by adding the logic to their business application but they were looking for a configuration variable such as those found in the core .yml file.
Attachments Open full size
What is meant by overload weaker devices? Is this a client-side or server-side issue? Are they talking about large page count or small pages that are very large in file size?
Attachments Open full size