[
https://issues.apache.org/jira/browse/IMAP-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707776#action_12707776
]
Robert Burrell Donkin commented on IMAP-80:
-------------------------------------------
"Although typically a server will support only a single Personal
Namespace, and a single Other User's Namespace, circumstances exist
where there MAY be multiples of these, and a client MUST be prepared
for them."
- RFC2342
I think it best to opt to add server support for a single Personal Namespace
and a single Other Users Namespace since I think this will result in a more
readable API. If necessary, this decision can be revised later.
> Allow MailboxManager to supply RFC 2342 "IMAP4 Namespace" meta data
> -------------------------------------------------------------------
>
> Key: IMAP-80
> URL: https://issues.apache.org/jira/browse/IMAP-80
> Project: JAMES Imap
> Issue Type: Improvement
> Components: Mailbox, Protocol
> Affects Versions: 0.1
> Reporter: Robert Burrell Donkin
> Assignee: Robert Burrell Donkin
> Fix For: 0.1
>
>
> RFC 2342 "IMAP4 Namespace" is currently hardcoded to return only a single
> Personal Namespace with a hard coded, default hierarchy deliminated.
> The specification allows multiple namespaces of the following types:
>
> * Personal Namespace
> * Other Users' Namespace
> * Shared Namespaces
> each of which may support separate hierarchy deliminators.
> This meta data may vary with the user. Clients typically query only once (at
> the start of a session) and it should be considered fixed for the duration of
> the session. Any changes in permissions should be dealt with by applying
> appropriate security dynamically.
> The current NAMESPACE implementation should be improved to allow the Mailbox
> implementation to supply this information.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
