[
https://issues.apache.org/jira/browse/JAMES-3203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17126447#comment-17126447
]
David Leangen commented on JAMES-3203:
--------------------------------------
I just attached an image. I will rewrite the text here because my handwriting
is so bad.
The idea that struck me when I viewed the image "[Using James as an IMAP
Server|http://james.apache.org/images/james-imap-server.png]" was:
It looks like the system is all about a "Mail" passing through a network of
functions. (Some functions may require long-lived sessions, yes.) A Mail is
provided as input, and then is "transformed" in one way or another as it is
output from the function.
A James Server is built by assembling these functional blocks in one way or
another.
Each block can be configured. By the way, configuring these functional blocks
is one way of changing the behaviour of the system, since configuring a block
changes its behaviour.
A Mailet Container can been seen as a means of organizing Mailets, but Mailets
are also similarly a functional block.
Of course, functions can have side-effects as well.
Is my observation correct?
I understand that James may not have been intended to be developed this way,
but it at least seems to act that way according to my current understanding.
> Provide more architecture pictures
> ----------------------------------
>
> Key: JAMES-3203
> URL: https://issues.apache.org/jira/browse/JAMES-3203
> Project: James Server
> Issue Type: Task
> Components: Documentation
> Reporter: David Leangen
> Priority: Major
> Attachments: IMG_0488.JPG
>
>
> Provide more images about the architecture in order to better explain James
> concepts.
> The idea for this issue [was presented on the mailing
> list|https://www.mail-archive.com/[email protected]/msg66051.html].
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]