[EMAIL PROTECTED] wrote:
> I would like to comment on this. I planned to write a NNTP
> server and a Instant messaging server that used Mailet or
> Mailet like API. I never looked close enough to *get* it. If
> this is a use you think the Mailet API is capable of
> covering then I will try to examine it by Sunday and get
> back to you. If the mailet API is not suitable just say so
> and I will not look at it :P. As I said I don't yet know
> enough about it - or my requirements for a NNTP/IM server.
My first reaction is to say that the mailet API probably isn't correct.
Mailet like API maybe, but not the mailet itself. The IM server will
probably be similar in some respect, but I'm not sure about the NNTP
server.
I think there are some good design lessons though in this (and the
servlet API). I think it is useful is to have xxxxxlets with config and
context objects, and the lifecycle (init/destroy) for the xxxxlet. This
keeps the system more independent. Beyond that, the unique of the
protocol only affects a small part of the API... servlets have
service(ServletRequest, ServletResponse), mailets have service(Mail),
and matchers have match(Mail) (hmm... maybe we should call them
matchlets.... nah...). I think once you figure out the basic way you
want your xxxxlets to affect the protocol, build the appropriate service
method and all the needed support classes.
Serge Knystautas
Loki Technologies
http://www.lokitech.com/
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives: <http://www.mail-archive.com/james%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
