[Kde-pim] Akonadi outbox & dispatcher agent [tentative design]

[Volker Krause]

On Sunday 03 May 2009 11:40:00 Ingo Klöcker wrote:
> On Sunday 03 May 2009, Constantin Berzan wrote:
> > * mailtransport needs a way to find all the resources (like
> > groupware) that can send mail.  Resources could provide dbus methods
> > like canSendMail() and sendMail(msgID), and mailtransport can query
> > each of them and if it canSendMail then put it into the combo box.
> > When asked to send a message using one of these transports,
> > mailtransport simply calls the appropriate method for the appropriate
> > resource, passing it the ID of the message in the outbox collection.
>
> I'm not sure why the indirection through mailtransport is needed. I
> would have thought that the dispatcher agent would talk to the
> appropriate resource. mailtransport would then only be used for the
> standard transports SMTP and sendmail. This would keep mailtransport
> (as low-level library) independent of Akonadi.

The advantage of making mailtransport aware of this is that we could keep 
using its UI elements for transport selection and configuration.

regards
Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20090503/b24a7d96/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/