Add CMSProcessableRandomAccessFile for RandomAccessFile-based CMS processing

[marijusGood]

Hi Team,

Currently, the CMS API provides CMSProcessableFile, which is useful when CMS content is backed by a File. However, there is no equivalent implementation for use cases where the data source is a RandomAccessFile.

This limitation makes it difficult to efficiently process large or partially accessed data streams without loading the entire content into memory or relying on non-public internal classes such as CMSProcessableInputStream.

Proposal:
Introduce a new public class, tentatively named CMSProcessableRandomAccessFile, modeled after CMSProcessableFile, but backed by a RandomAccessFile instead of a File.

Thanks!

[ralfhauser]

Is it correct that so far, CMSProcessableInputStream is only there to parse but not to create a signature ?

[peterdettman]

Could you expand a little on what would be gained by having a CMSProcessableRandomAccessFile? CMS doesn't do random access on the data, but just streams it all in one go, so I don't see what such a class would gain.

Generally you'd want to use the CMS*StreamGenerator classes when the data is large enough to worry about memory usage.

Note that in relation to CMSProcessableFile the API only deals with CMSTypedData and/or CMSReadable, so you are free to just add your own type that implements one or both of those interfaces according to your needs.