james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Burrell Donkin (JIRA)" <server-...@james.apache.org>
Subject [jira] Commented: (JAMES-714) SearchCommand: Modular Implementation...?
Date Sat, 02 Dec 2006 13:46:22 GMT
    [ http://issues.apache.org/jira/browse/JAMES-714?page=comments#action_12455094 ] 
            
Robert Burrell Donkin commented on JAMES-714:
---------------------------------------------

I agree that an solution optimised for torque isn't important. I would like a solution that
ensures enough information is passed to the backend to allow the backend to flexibly optimise
what it can. (FWIW i'm more interested in using JCRs than databases for email storage.) 

I agree that it would be better to parse the command into something other than SearchTerm's.
I think (as you suggest) the model needs to allow a basic (but slow) solution to be created
using SearchTerm's against MailMessage's but wonder whether this should be done by a translation
layer in the backend.

I think the best option would be for me to talk to my friend and use ANTLR to generate a parser
and then present the results as a patch. I suspect that the rest of the design may then become
clearer... 

> SearchCommand: Modular Implementation...?
> -----------------------------------------
>
>                 Key: JAMES-714
>                 URL: http://issues.apache.org/jira/browse/JAMES-714
>             Project: James
>          Issue Type: Task
>          Components: IMAPServer
>    Affects Versions: Trunk
>            Reporter: Robert Burrell Donkin
>            Priority: Minor
>
> The Search command is a part of the IMAP specification that is yet to be implemented
in James. The wiring has already been outlined with SearchCommandParser in SearchCommand returning
a SearchTerm implementation. All good so far.
> I need to implement a solution for a small number of search keys in order to allow my
IMAP server to be accessed by an Apple Mail.app client. (Not sure when I'll find the time
so opening a JIRA rather than discussing on list.)
> Implementing the complete Search command specification is likely to be time consuming.
However, the specification naturally breaks down into the composite application of a number
of search keys. So, it should be possible to factor the design so that each search key implementation
could be implemented in isolation. This would allow a partial implementation of the most commonly
used search terms to be build up over time.
> Opinions?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message