Daniel Sadolevsky wrote:
>
> Mailing list client processing example:
> Admin of list.working-dogs.com sets up a machine for running bots and sets
> up one of the bots to retrieve and send mail on behalf of
> [EMAIL PROTECTED] ,[EMAIL PROTECTED] and so
> on. As [EMAIL PROTECTED] ,this bot forwards messages it receives
> to all the recipients on the list.
> As [EMAIL PROTECTED] this bot replies to the mailing
> list registration requests and so on.
> I guess it can be done not on the server. Where am I wrong?
>
> Daniel
>
Not sure what you're talking about... this is how I think mailing list
should be managed server side:
<processor match="to=james@[localhost]" class="MailingList">
<listRepository> listRepository </listRepository>
<!-- queries listRepository to know which users are subscibed to the
list and expand the recipient to all these users --!>
</processor>
<processor match="to=james-on@[localhost]" class="MailingList">
<listRepository> listRepository </listRepository>
<!-- queries a private repository to know if this is the first
"subscribe mail" or the confirmation. If it's the first mail reply with
an id and store the username in the private repository. If it's a
confirmation add the user to the james listRepository --!>
</processor>
I don't see any client side work in it...
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]
