Mailing-List: contact server-dev-help@james.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "James Developers List" <server-dev@james.apache.org>
Received-SPF: pass (athena.apache.org: domain of pauloslf@gmail.com designates
 64.233.182.184 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=l+YTkN2Wl/NSxL2w7KstJCrEWeEgY2OwhbzUk0wJfIelUCi+cOpv1jHMa4a2hBt7uOSd+uUa8Ao6viXKZvbUpP1AxKaoHP7aYQpZwEMF64E8cWoMU90BHiY7U0HqctNcJlJMLciqr/dl9S//IKjvtbf8krLgLtAKquRBL0yWvds=
Message-ID: <efb949170711050836s669367acp53c69bc9dbdbe953@mail.gmail.com>
Date: Mon, 5 Nov 2007 16:36:34 +0000
From: "Paulo Sergio" <pauloslf@gmail.com>
To: "James Developers List" <server-dev@james.apache.org>
Subject: Re: [MailboxManager] API Design
In-Reply-To: <f470f68e0711050809g7341034dr418e73682ed7e7a8@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_10759_28212156.1194280594845"
References: <f470f68e0710261429r7e4ac447ia694e054c0d43648@mail.gmail.com>
	 <f470f68e0710301520k268cd9c3nb2529ded27961009@mail.gmail.com>
	 <2379623.21378141193824270208.JavaMail.root@elysia.void.it>
	 <f470f68e0711011256p68a8c205x71efcac6ac9aff2@mail.gmail.com>
	 <10642952.22470821193964871793.JavaMail.root@elysia.void.it>
	 <f470f68e0711021455o3b1b6635wa26b0cbe1d281f48@mail.gmail.com>
	 <a8fbd6780711030944v745e1c10t5589f02b9415a2f@mail.gmail.com>
	 <f470f68e0711040420r3ac8ab57i5fd77a10eeedcb32@mail.gmail.com>
	 <efb949170711041221x5de4f25cvb9f4975b20b55323@mail.gmail.com>
	 <f470f68e0711050809g7341034dr418e73682ed7e7a8@mail.gmail.com>

------=_Part_10759_28212156.1194280594845
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi Robert,

On 11/5/07, Robert Burrell Donkin <robertburrelldonkin@gmail.com> wrote:
>
> On Nov 4, 2007 8:21 PM, Paulo Sergio <pauloslf@gmail.com> wrote:
> > Hi all,
>
> hi paulo
>
> > i've been following the  discussion  and  i would like to give my
> opinion
> > (although i'm not an expert).
> > i think we are forgetting an important thing, we are designing an API
> > thinking about the existent protocols, although i think we should think
> also
> > in  what's next :) .
> >
> > In my case, i'm currently working in a web-service backend for james
> using
> > IMAP as a "front end protocol". Now i would like to start working in a
> push
> > mechanism, and i think about implementing IMAP Idle, i would have a
> server
> > sending the notification to james server, witch then would send the
> > notification to the client.
> >
> > Well, this is one of the problems i think james has (correct me if i'm
> > wrong), it lacks any type of push mechanism.
> > In my case the server could send a session id to james, indicating what
> > client should retrieve the new mails, the problem would be to get the
> > session of the user that should be notified..
> >
> >
> > in my opinion i believe we should have some king of way of sending a
> > notification/event to the mailbox or even  better to any session, these
> > would be send by an external server (my case) or by events sent by james
> > server (ex:  when a message is received, check if the user is connected
> and
> > if it is send a notification to the session)
>
> ATM the API allows mailbox listeners to be registered but the current
> interfaces aren't great. a single method accepting an event is more
> concise and extensible than including all calls in an interface.
>
> IDLE was touched upon earlier. Zsombor suggested that listeners would
> registered at the mailboxmanager level. if the API were switched to
> use events then every listener could receive events for every mailbox
> and then ignore any that were of no interest. novel events could be
> injected into the system by the backend implementation. listeners
> would ignore any events they did not understand.
>
> would this mechanism be good enough?


i believe so, but you mean  that each  user connected would be able to
register as a listener and then be notified when something happens?
what about notifications from an external service ? how will these work?

Thanks,
paulo f

another open question is whether an explicit API session would be a
> useful to tie things together. something like a session would probably
> be needed to reduce the number of factory method calls required to
> obtain an API for a particular mailbox.
>
> - robert
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>

------=_Part_10759_28212156.1194280594845--