[
https://issues.apache.org/jira/browse/JAMES-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538182
]
Robert Burrell Donkin commented on JAMES-806:
---------------------------------------------
The reason why there are two IdRanges is to do with the restructuring and
modularisation.
The newer SEDA implementation that interests me is based on an isolated fork of
the older command-based implementation. Both are independent components. So
though there are some classes with identical names, they are in different
packages and the build process prevents co-dependencies.
Both functional components (as well as backend implementations) depend on the
Mailbox API but the Mailbox API should not depend on them (and so introduce a
cyclic component dependency). This is easy to fix - add a new value object
(NumericRange, say) into SearchParameters and use that rather than either
IdRange. This means a little more work but IMHO it's worth it to retain a
generic API.
> Search command implementation
> -----------------------------
>
> Key: JAMES-806
> URL: https://issues.apache.org/jira/browse/JAMES-806
> Project: James
> Issue Type: Improvement
> Components: IMAPServer
> Affects Versions: Trunk
> Reporter: Zsombor Gegesy
> Assignee: Robert Burrell Donkin
> Fix For: Trunk
>
> Attachments: search.patch
>
>
> Currently the search command is not implemented in the frontend side, this
> need to be fixed, ASAP! :)
--
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]
