[MIME4J-83] Add a more generic machanism for storing message bodies

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 0.5
• Fix Version/s: 0.6
• Assignee: Unassigned
• Reporter: Markus Wiederkehr
• Created: 27/Oct/08 14:38
• Updated: 04/Feb/09 20:50
• Resolved: 22/Nov/08 13:30

Description

Currently Mime4j uses TempStorage, TempPath and TempFile to store the contents of a text or binary body of a message. While this design allows for TempStorage to be replaced with a custom implementation it does not seem to be generic enough.

A TempStorage implementation may choose to keep the data in memory but it still has to deal with things like file name prefixes/suffixes or creating subdirectories. The entire interface TempPath and many methods in TempFile seem to be unnecessary.

Also while an application can configure what TempStorage instance it wants to use (by means of a system property and a static setInstance method) there is no way to inject a TempStorage instance into a MessageBuilder.

An alternative storage mechanism should be simpler and more generic. It should be possible to provide implementations that store the data in memory or on disk in the system's temp folder for example. Other implementations could keep the data in memory as long as a certain threshold size does not get exceeded or use a specific folder on disk to store the files.

Issue Links

• relates to: MIME4J-91 Add OutputStream support to StorageProvider