[prev in list] [next in list] [prev in thread] [next in thread] 

List:       james-dev
Subject:    Re: JMS for spooling
From:       Norman Maurer <norman.maurer () googlemail ! com>
Date:       2010-02-28 18:15:43
Message-ID: 75bda7a01002281015i506310e8s6708899ff2f29b19 () mail ! gmail ! com
[Download RAW message or body]

Ok first version of JMS spooling is in trunk now.. Its far from
perfect performant-wise. But It shows the idea..

Bye,
Norman

2010/2/25 Norman Maurer <norman.maurer@googlemail.com>:
> true enough.. But let us first do the jms spooling.. then cut M1.
>
> I will start to commit changes to trunk then.
>
> Bye,
> Norman
>
> 2010/2/24 Stefano Bagnara <apache@bago.org>:
>> 2010/2/24 Robert Burrell Donkin <robertburrelldonkin@gmail.com>:
>>> On Wed, Feb 24, 2010 at 8:27 PM, Norman Maurer <norman@apache.org> wrote:
>>>> Hi all,
>>>>
>>>> I started to work on a JMS implementation for spooling in JAMES. Its
>>>> workin but still more a POC then anything else. Anyway I would like to
>>>> commit it to work on it in svn and do small commits. Because its not
>>>> stable yet and not production ready should I better use a sandbox and
>>>> merge it later ? or are the others ok with having some "in progress"
>>>> trunk ?
>>>
>>> i'm a big fan of making progress in trunk. even when 3 is production
>>> ready, i would much prefer to see trunk push ahead and take production
>>> branches off it.
>>
>> +1
>>
>> Stefano
>>
>> ---------------------------------------------------------------------
>> 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

[prev in list] [next in list] [prev in thread] [next in thread]