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: [PROPOSAL] Using Camel as replacement of MailProcessor / SpoolManager
Date Mon, 22 Feb 2010 20:14:45 GMT
The POC is now in trunk. I'm using in production since today and so
far I don't see any problems.

I think I will now start to tackle the jms stuff and remove "old" code..

Bye,
Norman




2010/2/19 Norman Maurer <norman.maurer@googlemail.com>:
> Hi Robert,
>
> I 100% agree with you. But I think thats something we could take care
> of once the camel routing stuff is in place..
>
> Bye,
> Norman
>
> 2010/2/18 Robert Burrell Donkin <robertburrelldonkin@gmail.com>:
>> On Thu, Feb 18, 2010 at 8:22 PM, Mario Zsilak <mario.zsilak@inew-cs.com> wrote:
>>> Hi,
>>>
>>> I just took a glance at camel.apache.org but I spotted the following
>>> statement:
>>>
>>> <!--    start -->
>>> Apache Camel can be used as a routing and mediation engine for the following
>>> projects:
>>>
>>>    * ...
>>>    * Apache ActiveMQ which is the most popular and powerful open source
>>> message broker
>>>    * ...
>>> <!--     end    -->
>>>
>>>
>>> I guess that means that other message brokers (including commercial ones)
>>> are not supported within Apache Camel?
>>> In that case I would be happy to see some kind of abstraction layer so that
>>> others (like me) can implement their own stuff ...
>>>
>>> Apart from my requirements I guess most people don't need these (very nice)
>>> features at all.
>>> However if there is a performance gain, especially when using only 1
>>> server/james-instance, we should go for it.
>>
>> IIRC we've discuss this before and the consensus was that an API would
>> be the right way to go
>>
>> +1 with a few comments
>>
>> might need to think a little about big emails. might be better just to
>> send the meta-data around keeping a reference to a data store. this
>> would fit in with ideas about streaming bodies more directly into
>> storage.
>>
>> - 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