Robert Burrell Donkin (JIRA) ha scritto: > [ > https://issues.apache.org/jira/browse/MIME4J-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12518011 > ] > > Robert Burrell Donkin commented on MIME4J-23: > --------------------------------------------- > > Optional may be better than dropping. There are times when good enough is > best when dealing with emails. > > Perhaps monitor pattern (recording them as events) would be useful
I never used the monitor pattern for server side libraries, but I'm interested in how it could apply to this scenario. >From a developer perspective it seems to be more easy to receive exceptions on failure when a strict parsing is enabled, but maybe both solutions can be enabled providing a wrapper that will parse the message, listen for events and throw exceptions when a given event is received. BTW I'll wait for some code to review ;-) Stefano >> [JW#3] Drop lazy syntax checking or make it optional >> ----------------------------------------------------- >> >> Key: MIME4J-23 >> URL: https://issues.apache.org/jira/browse/MIME4J-23 >> Project: Mime4j >> Issue Type: Wish >> Reporter: Robert Burrell Donkin >> >> http://mail-archives.apache.org/mod_mbox/james-server-dev/200708.mbox/[EMAIL >> PROTECTED] #3 >> 3.) Drop lazy syntax checking or make it optional >> Mime4j has a lot of places where it detects syntax errors of the >> multipart stream. Currently, these are reported by a warning message, >> which is being logged. >> This behaviour is improper. Such situations should cause an >> exception or at >> least the Mime4j user should be able to request that they do. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
