Robert Burrell Donkin ha scritto: > for example, in the current API to perform an operation, it's > necessary to create a session. however, sessions are heavyweight: > performing extensive pre-emptive caching. this is fine when dealing > with heavyweight session oriented front ends but not so good for > lightweight front ends. IMAP is session oriented but this design > decision in the MailboxAPI results in poor performance for any calls > that do not run against the selected session.
How do you handle transactions if you don't use a Session or a similar concept? IMHO one of the missing things in JAMES Server is transaction support. When a processor run a mail through a single step (a mailet) it should either completely fail or completely succeed. How do you plan to support a simple LIST, RETR, DELE scenario without a session? The list gives you identifier that are valid only in that session, the following retr and the dele must use the same numbers. Are you simply saying that MailboxManager should be stateless and the session should be managed on top of this? Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
