james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Soren Hilmer <soren.hil...@tietoenator.com>
Subject Re: Repositories
Date Wed, 22 Dec 2004 15:01:58 GMT
Is it not the case that CornerStone is no longer actively maintained (or is it 
just Avalon) In which case I would prefer moving them into James.

If CornerStone is alive and well, submitting the code back would be a good 
move. 
But If my memory does not fail me completely (I often get the issues on 
Phoenix and CornerStone and Avalon mixedup in my head) the current James 2.1 
branch is stuck with an old CornerStone build (actually one that is not even 
tagged in the CornerStone-CVS, so we cannot recreate it) in which case we 
also need to put the code into James.

So the short story IMO is, put it into James and submit it back if it makes 
sense (the two implementations may of course differ depending on the 
CornerStone version).

--Søren


On Wednesday 22 December 2004 15:22, Jason Webb wrote:
> > -----Original Message-----
> > From: Soren Hilmer [mailto:soren.hilmer@tietoenator.com]
> > Sent: 22 December 2004 14:15
> > To: James Developers List
> > Subject: Re: Repositories
> >
> > On Wednesday 22 December 2004 13:50, Danny Angus wrote:
> > > Soren,
> > > Derby would be embedded in James, it would not be visible to users at
> >
> > all,
> >
> > > and require no additional admin or configuration.
> > > The messages would not be visible in the filesystem, but that would be
> >
> > the
> >
> > > only drawback.
> >
> > Okay, sounds a little better.
> >
> > Still I must say I prefer the file repositories, it is a lot easier to
> > support
> > a mailserver when you can read the mails currently in process directly
> > from
> > the filesystem.
> > This is AFAIK also the approach serious mailservers like Postfix does
> > things.
> >
> > If we go for an all DB solution. We need better tools to show the
> > repositories
> > and messages within them.
> >
> > I can see the problems about destroying/renaming repositories, because
> > those
> > operations are not supported by CornerStone.
> >
> > Could it be a compromise that we require DB repositories only when IMAP
> > is used, and thereby allowing existing setups to continue with
> > file/filedb repositories?
>
> One repository to rule them all, one repository to find them. One
> repository to rule them all and in the darkness bind them :) (Apologies to
> JRR
>
> One of my primary design goals is to make sure the user can access their
> email using POP3 or IMAP4 in whatever way they choose. I will implement the
> file based repositories to have the required methods for IMAP. This will
> involve changes to the cornerstone classes. Is the best thing to do with
> these changes to move them into James proper or to attempt to submit
> changes to the Cornerstone project?
>
> > --Søren
> >
> > > d.
>
> <snip'd>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
> For additional commands, e-mail: server-dev-help@james.apache.org

-- 
Søren Hilmer, M.Sc.
R&D manager		Phone:	+45 72 30 64 00
TietoEnator IT+ A/S	Fax:	+45 72 30 64 02
Ved Lunden 12		Direct:	+45 72 30 64 57
DK-8230 Åbyhøj		Email:	soren.hilmer <at> tietoenator.com

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