james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benoit Tellier <be...@minet.net>
Subject Re: server/data/data-memory (was : Re: My thoughts on JMAP implementation)
Date Mon, 14 Dec 2015 09:56:29 GMT
In my JAMES-1618 PR I introduced an imMemory UsersRepository (as I
wanted to test SieveRepository integration).

Le 14/12/2015 08:45, Matthieu Baechler a écrit :
> 
> 
> On 13/12/2015 12:43, Tellier Benoit wrote:
> 
>>   - Why not introducing /server/data/data-memory for your
>> MemoryAccessTokenRepository ? I have upcoming commits to create the
>> project, maybe moving it to data-memory would make sens.
> 
> The only rational for not doing it yet is to avoid project
> proliferation. We only have a single class in data-jmap for in-memory
> implementation.
> 
> If you create a server/data/data-memory project, we can put
> MemoryAccessTokenRepository in it, that's cool.
> 

I want to ask a really stupid question : "Is project proliferation a bad
thing?"

 - What we pay is time to run tests and compile. Small projects that
take ~ 2 s to compile do not seem that expensive.
 - If projects are well organized in a hierarchical structure, we are
not lost, as we can redirect our selves to the right project.
 - We should pay attention to code duplication (more on that in my next
mail )

 - What is dangerous is project for backends nobody is able / volontary
to maintain...

My opinion.

---------------------------------------------------------------------
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