> Let me state another usecase...the current file format of the
naglist was a
> suggestion that I made to Sam. It is structured in a messaging
service type
> format [1]. The point being that it would be nice to have a "Nagging
> Service" sitting out listening on a Messaging Server somewhere who's
job it
> is to receive "nag messages" and sent the appropriate emails or
other
> formats based on them. That way *anything* could create *anything*
to nag
> about.
>
> Yes, I know that the format of the file could be derived from
anywhere, but
> the point being that I'm working towards KISS here. :-)
>
> [1] http://elvin.dstc.edu.au/intro/what.html
>
Yet another good idea jon, a generic notification server. Just code
up a servlet to process a POST request, and whammo, done. I think I
might just have to write it ;-)
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
