There would be a main service thread witch would monitor the
status off all the worker threads..
basically, if the design were kept the way it is now (ie, declude called
on each delivery of a email)
declude starts. , isolates email, create worker threads to perform tests..
(ie, while
one thread can be performing dns tests, another could be doing sniffer,
while another
is virus actions) when each "Worker" thread is complete it can notify the
parent thread.
and threading is fun, you pretty much have everything in place to
communicate back
and forth between processes. allowing many instances of declude to talk to
each other.
----- Original Message -----
From: "Darin Cox" <[EMAIL PROTECTED]>
To: <Declude.JunkMail@declude.com>
Sent: Wednesday, August 24, 2005 8:54 AM
Subject: Re: [Declude.JunkMail] IMail 8.02
RSP> "...allow E-mails that are being processed to communicate with one
another"
Curious. How do emails communicate with each other?
Darin.
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
---
This email has been scanned for possible viruses by Declude Antivirus.
For more information on Declude Antivirus, Visit www.declude.com
---
This email has been scanned for possible viruses by Declude Antivirus.
For more information on Declude Antivirus, Visit www.declude.com
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
