[jira] Created: (JAMES-770) Exception when runnning JAMES with run.sh

2007-01-24 Thread maximeloridan (JIRA)
Exception when runnning JAMES with run.sh - Key: JAMES-770 URL: https://issues.apache.org/jira/browse/JAMES-770 Project: James Issue Type: Bug Affects Versions: 2.3.0 Environment: windows,

[jira] Updated: (JAMES-770) Exception when runnning JAMES with run.sh

2007-01-24 Thread maximeloridan (JIRA)
[ https://issues.apache.org/jira/browse/JAMES-770?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] maximeloridan updated JAMES-770: Attachment: james.jpg > Exception when runnning JAMES with run.sh >

Re: MailboxManager API and session orientation was: Jsieve Configuration

2007-01-24 Thread robert burrell donkin
On 1/23/07, Serge Knystautas <[EMAIL PROTECTED]> wrote: I would suggest looking briefly at the raw IMAP protocol. It makes the protocol nasty, but every command gets a unique token so that requests and responses are asynchronous. I would presume this is why someone like Andy will question th

Re: MailboxManager API and session orientation was: Jsieve Configuration

2007-01-24 Thread robert burrell donkin
On 1/23/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote: robert burrell donkin wrote: > commands that rely on or change message ID must be serialized and > executed in the order that the client has sent them. Ok now I understand the issue. I started from the, now I understand wrong, assumption tha

Re: MailboxManager API and session orientation was: Jsieve Configuration

2007-01-24 Thread Stefano Bagnara
Serge Knystautas wrote: On 1/23/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote: Can you make a common case example where the need of multiple concurrent processors is needed for a single client? (if I have a concrete case I remember better the issue in later discussions) - You have 2 emails in

Re: MailboxManager API and session orientation was: Jsieve Configuration

2007-01-24 Thread robert burrell donkin
On 1/22/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote: robert burrell donkin wrote: >> Initially I thought this thread was about 3, while your diagrams seems >> to me about 1: this is why I'm confused. > > the diagram concerns the interface between the handler and processor > layers (as defined a

[jira] Commented: (JSIEVE-13) How to configure JSieve with JAMES?

2007-01-24 Thread Steve Brewin (JIRA)
[ https://issues.apache.org/jira/browse/JSIEVE-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467128 ] Steve Brewin commented on JSIEVE-13: A colleague of yours has already asked a similar question. Please see http:/

[jira] Resolved: (JSIEVE-13) How to configure JSieve with JAMES?

2007-01-24 Thread Steve Brewin (JIRA)
[ https://issues.apache.org/jira/browse/JSIEVE-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Steve Brewin resolved JSIEVE-13. Resolution: Invalid Not a an issue. Its a request better directed to the dev list. > How to configu

Re: MailboxManager API and session orientation was: Jsieve Configuration

2007-01-24 Thread robert burrell donkin
On 1/24/07, robert burrell donkin <[EMAIL PROTECTED]> wrote: On 1/23/07, Stefano Bagnara <[EMAIL PROTECTED]> wrote: > robert burrell donkin wrote: (i've had a chance to take a look at the rfc) > What about multiple IMAP clients accessing the same imap folder? Are > message identifiers diffe

svn commit: r499599 - in /james/server/sandbox/design-doodles/imap/messaging-api: ./ i1/ i2/

2007-01-24 Thread rdonkin
Author: rdonkin Date: Wed Jan 24 14:39:34 2007 New Revision: 499599 URL: http://svn.apache.org/viewvc?view=rev&rev=499599 Log: Second iteration of IMAP design Added: james/server/sandbox/design-doodles/imap/messaging-api/i1/ james/server/sandbox/design-doodles/imap/messaging-api/i1/imap-

Re: MailboxManager API and session orientation was: Jsieve Configuration

2007-01-24 Thread Serge Knystautas
On 1/24/07, robert burrell donkin <[EMAIL PROTECTED]> wrote: On 1/23/07, Serge Knystautas <[EMAIL PROTECTED]> wrote: > I would suggest looking briefly at the raw IMAP protocol. It makes > the protocol nasty, but every command gets a unique token so that > requests and responses are asynchrono