I have thought about the issue expressed on the last occasion and I am
afraid I couldn't think of anything sufficient or compelling. Any
further comments from me on this subject are not suitable because it
wouldn't be a comment, it would be an essay and the basis for a new
project. It would certainly be a useful project (and one I should do)
for James in the future (particularly runtime management) but at present
it lacks the qualities required to add value to James V3.
I think 'Service' terminology is going in the right direction, James is
referred to as a mail 'Server' however I would consider the container to
be the Server and James a Service. I don't think I have much better to
add than that at present.
Regards,
Simon
On 28/10/10 07:47, Eric Charles wrote:
Hi Simon,
If you look for example to the ActiveMQ JMS Queue used by james, we
may imagine the bus can deployed on different servers, with each
servers serving some incoming smtp requests, and injecting the mails
in the distributed JMS queue.
We could also imagine create some james images to be deployed in EC2.
When james will be OSGIed, it could be deployed in a distributed OSGI
solution (newton,... or whatever).
So yes, I can be with you about the notion of "Cloud of components"
or "Component Cloud" for james.
I suppose this kind of topic have already been discussed around.
For james, I would see (thinking loud) something like MaS (Mail as a
Service) in a future.
Back to basics, we are still willing to find a place/name for the
SpoolManager and JamesServer.
You can read more on James architecture and development on these very
alpha pages:
- http://james.apache.org/server/3/dev_architecture.html
- http://james.apache.org/server/3/dev_build.html
- http://james.apache.org/server/3/dev_extend.html
Tks,
Eric
On 23/10/2010 17:47, Simon Funnell wrote:
The last time I commented on such things I went a little wild and
spewed a bit too much. I will keep it more succinct this time but it
is worth saying.
I think the use of the word 'container' is a really bad term to use
for expressing the notion of modern networked software.
If I was to put in my two cents I would say James server is a
'synergistic and empathetic network of components arranged as a
modular enterprise mail server'.
Container terminology use is profuse so it might be difficult to use
other terms. I do think it would be worth discussing what it 'is'
exactly because I think container suggests a particular viewpoint
where another might be more appropriate.
Actually, as I sit here writing I might have had an idea, what about
'Cloud of Components' or 'Component Cloud' with all this cloud
computing business about at present.
Could it be that James Server is a Component Cloud of type Modular
Enterprise Mail Server?
I don't know if that's a joke or if I am actually being serious.
Regards,
Simon
Align packages hierarchy of the services
----------------------------------------
Key: JAMES-1074
URL: https://issues.apache.org/jira/browse/JAMES-1074
Project: JAMES Server
Issue Type: Improvement
Affects Versions: 3.0-M1
Reporter: Eric Charles
Assignee: Eric Charles
Fix For: 3.0-M1
We need to align package service hierarchy to have stable api,
uniformity and osgi-deployable.
For example, the proposed hierarchy for a "mail" service is:
org.apache.james.mail.api (in the mail api project)
org.apache.james.mail.lib (in the mail library project)
org.apache.james.mail.jpa (in the mail jpa impl project)
org.apache.james.mail.jcr (in the mail jcr impl project)
....
The conf files and spring-beans.xml need to be updated according to
the repackaging.
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
