That's my problem. I think that linear pipe processing is really to
simple to allow easy managing of common needs and here my example:
Let's suppose I have 100 account on my machine and I want to provide
each user with some standard mailet to manager their own inbox. Each
user can configure a Forward, ImOnVacation, a Filter, a Mail2Fax and a
Mail2Wap mailet. This makes 500 mailet configuration that can change
pretty often. I DONT WANT THEM to be in the main processing pipe.
My picture should be: I set a mailet that acts like a sub processing
pipe. And I'd like to see just one of this SubPipeMailet for all users
so that if I add an account I don't need to change tha main processing
pipe configuration.
... _______________ |--|Forward|
| | | |
0-match-------------| SubPipeMailet|-0-match-----------|ImOnVacation|
| (All local users) |______________| (each user |
| one at a time)|--|...|
...
This picture look fine to me since I can manage each user configuration
the way I prefer (with some private ad hoc configuration) and I can
easily add or remove accounts.
The problem is that the SubPipeMailet needs to return more than one Mail
object.
If a Mail goes in with two local recipients each body will be processed
differently and I will have two Mail to return to the mail pipe.
Is there a turn around or we need to define a Mailet extension with some
Mail[] service(Mail)?
Fede
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/>
Problems?: [EMAIL PROTECTED]
