On 11/10/06, Stefano Bagnara <[EMAIL PROTECTED]> wrote:
I think the proposals described there are too much XML intensive and they depends on plans about the mailet apis. I would like to keep this issue as a simple backward compatible change.
Any change to James implementation which doesn't require an API change would work for me. Like you say we've known for a long time that this needs to change in the API, but it is tied up with the whole model of matcher->mailet, one of the considerations is that it may make sense to allow more than one matcher to be combined, for e.g. "HostIsLocal AND SMTPAuthSuccessful" There's also some idea that the relationship could change to the mailet being a property of the matcher instead of the other way around, e.g. IF(matcher1 AND matcher2) THEN mailet1 mailet2 ELSE mailet3 Of course this would need to be structured as a declared assembly of reusable components and not as a language, or we may as well just write code, but XML does provide us with a number of useful techniques which can be used for declaring and assembling, d. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
