Roberto Lo Giacco wrote:
>
> I was thinking that Mailet != HttpServlet and Mailet extends Servlet... I'm
> asking myself I wasn't out too much time from the discussion....
I was of this idea myself, but after long reasoning, I came to the
conclusion that the Servlet API has wrong design patterns that do not
allow us to extend Servlet and add Mail capabilities.
Why? because the Servlet API was created for HTTP then abstracted later.
This allowed them to remove all HTTP dependencies from javax.servlet,
but left them with the idea of a generic request/response protocol where
the response is sent back directly to the requestor.
This is not what happens for SMTP where the mailet response is sent to
somebody else.
javax.servlet is not abstracted enough to handle both cases.
And the Servlet Expert Group doesn't care about mail extentions to
servlets enough to patch these protocol abstraction problems even
because this would mean creating huge back incompatible changes.
Also, knowing the JCP process, I'd rather maintain the API here than
anything with javax. in front... also, the XMl API show that it doesn't
matter what extention you have in front, but if an API is useful and
good it gets accepted and used by all. (just like SAX)
This is why I think Mailet != MailServlet and we should not aim for
integration.
I know it's sad, but I don't want to spend any more energy into this so
we take our own path and live well.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
Missed us in Orlando? Make it up with ApacheCON Europe in London!
------------------------- http://ApacheCon.Com ---------------------
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/>
Problems?: [EMAIL PROTECTED]
