[
https://issues.apache.org/jira/browse/JAMES-806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12538189
]
Zsombor Gegesy commented on JAMES-806:
--------------------------------------
I can't understand how the multi-threading issue related to have the following
classes/interfaces:
ImapProcessorFactory, DefaultImapProcessorFactory, a lots of ImapProcessor, a
lots of org.apache.james.imap.command.imap4rev1.*Command class, a lots of
ImapResponseMessage and
org.apache.james.imap.message.request.imap4rev1.*Request. I'm not against
object orientated designs, but it seems to much for no benefit. And I know,
that the same client can have multiple connections to the same server, but i
don't see, how the current simpler design, with one type of ImapResponse and
ImapRequest class, and lot's of Command class cant handle the problem. I know,
the IDLE command need some planning, and synchonization between the threads for
the output queue.
> 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]