Last days I was wondering what is the best way to define mail servlet
interface.
I looked both at Serge implementation and Stefano and Pier Mail Servlet
draft and I realyze there is a limitation: both definitions allow a mail
servlet to receive only one mail as "request" and generate only one
"response".
This is enought for mail servlet like a mailinglistservlet which only,
from the request message, expand recipient list and add some footer.
My point is: do we need a mail servlet to produce more than a response
from an incoming message?
I was thinking to something like a mailservlet whitch examine incoming
messages and produce a new mail if some condition occurs. In this case
one message enter the mail servlet and one or two (the old untoched
message and the new one) different messages exit.
Another example can be some translation servlet which translate incoming
messages to the user preferred language:
I can write
<processor match="to=mario@[localhost] or to=natasha@[localhost]"
class="Translator">
<translate user=mario language=italian/>
<translate user=natasha language=russian/>
</processor>
This meand the servlet take the same message sent to mario and natasha
and produce two different output messages.
Since such things cannot be done using both Serge or Pier and Stefano
pattern I was wandering if someting more powerful could be needed.
Am I on the right way or just thinking too big?
Federico
*-----------------------------------*
"Troubles occurr when two people try
to be intelligent in the same time."
- Murphy
*-----------------------------------*
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/>
Problems?: [EMAIL PROTECTED]
