[MIME4J-154] ContentHandler should rely on MimeStreamParser.setContentDecoding instead of dealing with their own transfer decoding code.

• Type: Improvement
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 0.6
• Fix Version/s: 0.7
• Assignee: Stefano Bagnara
• Reporter: Stefano Bagnara
• Created: 30/Dec/09 14:06
• Updated: 30/Jan/10 19:16
• Resolved: 30/Jan/10 19:16

Description

Both MessageBuilder and SimpleContentHandler have special code to recognize the transfer-encoding and decode the inputstream using the Base64InputStream or the QuotedPrintableInputStream. This is a worse practice as MimeStreamParser now have the setContentDecoding, so the caller should simply set that property to true and the content handler will receive decoded streams.

We should "hide" the common task behind a single entry point. The fewer classes we ask to use to our downstream users, the easier will be to track compatibility, upgrading, and so on. If to use mime4j in basic ways people have to create classes from all of our packages then it will be a PITA.