I'm curious about people's thoughts about the James Mailet API as a design for e-mail processing after it's been accepted by the SMTP server. (The api is described at http://james.apache.org/mailet_api_2_1.html)
Since I've already received Andy's views on this, I'd like to hear from others about the technical merits and demerits of the API. Of course, if I ask the James mail list about it, they'll generally rave. I'm equally fearful that asking this question here could yield negative responses simply because James is an Apache project, and Apache is doing Geronimo, and JBoss people seem to be a bit touchy about giving credit to an Apache project. Still, I truly would like to hear non-religious, technical arguments for or against the Mailet API. Honestly, I'm asking for your views because I'm considering the efficacy of borrowing from that API, and from the JBoss SMTP/POP server code, to produce a Mailet-based e-mail processor in JBoss. This will be a private initiative since it's clearly not a preferred solution desired by Andy. However, there are a lot of James users who might welcome a J2EE-based solution, especially now that Avalon is tango uniform. My thanks (and apologies for any ruffled feathers) are extended in advance. Jack View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870612#3870612 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870612 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
