I may fail to see the big picture. At the moment it looks like the receiver (protocol) for a mail needs to decide which mail listeners a mail is sent to.
Perhaps we should rather follow the MBean+MBeanServer pattern, where the receivers (detached invokers) send the mail into a routing kernel (MBeanServer) which decides what to do with the mail. On the path between receiver and kernel, interceptors could do mail manipulation like canonicalisation (sp?) of headers or tagging as possible spam. My code will do bound-fetchmail, but when you call it from a (to be written) scheduler mbean, it can do multiuser. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3870882#3870882 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3870882 ------------------------------------------------------- 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 JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
