james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Norman Maurer <norman.mau...@googlemail.com>
Subject Re: MailRepository and MailboxManager
Date Fri, 12 Feb 2010 10:26:44 GMT
Sounds good,

so what about some code to show your "general" idea ?

Bye,
Norman

2010/2/12 Robert Burrell Donkin <robertburrelldonkin@gmail.com>:
> On Thu, Feb 4, 2010 at 9:08 PM, Norman Maurer
> <norman.maurer@googlemail.com> wrote:
>> <SNIP>
>>
>> 2010/1/22 Robert Burrell Donkin <robertburrelldonkin@gmail.com>:
>>
>>> maybe:
>>>
>>>  deliver(String URL, Mail mail)
>>>
>>> would be a reasonable first step. (i agree that we need to revise Mail
>>> but i think that can wait.)
>>>
>>> URL gives more flexibility for virtual stuff and namespacing. for both
>>> IMAP and POP3 the storage of the read only raw data is logically
>>> independent from the read-write meta-data that's need to manage the
>>> mail. i suspect that the optimal performance would be to combine a
>>> flexible data store for the meta-data and file or http for the raw
>>> data.
>>>
>>> examples
>>>
>>> deliver("james://username@localhost/", mail)
>>>
>>
>> I think we could even use it for deliver via smtp to remote host:
>>
>> deliver("smtp:mail.whatever.de",mail)
>>
>> WDYT ?
>
> sounds good :-)
>
> i like the idea of being able to compose the processor from factored
> out handlers and register them by protocol
>
> opinions?
>
> - robert
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message