You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "Tim-Christian Mundt (JIRA)" <se...@james.apache.org> on 2010/07/05 18:35:49 UTC
[jira] Created: (IMAP-179) delimiter does not need to be
configurable
delimiter does not need to be configurable
------------------------------------------
Key: IMAP-179
URL: https://issues.apache.org/jira/browse/IMAP-179
Project: JAMES Imap
Issue Type: Improvement
Reporter: Tim-Christian Mundt
There is - as far as I can see - no need to ever change the hierarchy delimiter. Storage implementations can still choose whatever delimiter they want to choose or how to represent the hierarchy. Hence, it would be much easier and cleaner to simply define a constant (or better use the existing one). This is also part of solving issue https://issues.apache.org/jira/browse/IMAP-168
--
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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Commented: (IMAP-179) delimiter does not need to be
configurable
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/IMAP-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12885280#action_12885280 ]
Norman Maurer commented on IMAP-179:
------------------------------------
I'm with you here.. I will remove the configurable nature of it
> delimiter does not need to be configurable
> ------------------------------------------
>
> Key: IMAP-179
> URL: https://issues.apache.org/jira/browse/IMAP-179
> Project: JAMES Imap
> Issue Type: Improvement
> Reporter: Tim-Christian Mundt
>
> There is - as far as I can see - no need to ever change the hierarchy delimiter. Storage implementations can still choose whatever delimiter they want to choose or how to represent the hierarchy. Hence, it would be much easier and cleaner to simply define a constant (or better use the existing one). This is also part of solving issue https://issues.apache.org/jira/browse/IMAP-168
--
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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org
[jira] Resolved: (IMAP-179) delimiter does not need to be
configurable
Posted by "Norman Maurer (JIRA)" <se...@james.apache.org>.
[ https://issues.apache.org/jira/browse/IMAP-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Norman Maurer resolved IMAP-179.
--------------------------------
Assignee: Norman Maurer
Fix Version/s: 0.1
Resolution: Fixed
Removed the possiblity to specify the delimiter
> delimiter does not need to be configurable
> ------------------------------------------
>
> Key: IMAP-179
> URL: https://issues.apache.org/jira/browse/IMAP-179
> Project: JAMES Imap
> Issue Type: Improvement
> Reporter: Tim-Christian Mundt
> Assignee: Norman Maurer
> Fix For: 0.1
>
>
> There is - as far as I can see - no need to ever change the hierarchy delimiter. Storage implementations can still choose whatever delimiter they want to choose or how to represent the hierarchy. Hence, it would be much easier and cleaner to simply define a constant (or better use the existing one). This is also part of solving issue https://issues.apache.org/jira/browse/IMAP-168
--
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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org