EventQueuingSessionMailbox provides an alterative way to access information available to message listeners. too many alternative mechanisms to achieve the same function within an API smells bad: too often it's a sign of a rambling API in need of pruning.
the API implementor does not know a priori whether a client will call these methods. not every protocol will need access to this information. typically, the message results from every event will have to be cached in case they will be called at some time in the future. it would be more natural for protocol sessions to register mailbox listeners and cache any information they require and POJO mailbox listeners with the current EventQueuingSessionMailbox function provided. EventQueuingSessionMailbox could then be eliminated. opinions? - robert 1.http://svn.apache.org/repos/asf/james/server/trunk/core-library/src/main/java/org/apache/james/mailboxmanager/mailbox/EventQueueingSessionMailbox.java --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
