head	1.1;
access;
symbols
	release-2-3-0-final:1.1
	release-2-2-6-final:1.1
	release-2-2-5-final:1.1
	release-2-2-4-final:1.1
	release-2-2-3-final:1.1
	release-2-2-2-final:1.1
	release-2-2-0-final:1.1
	release-2-1-0-rc3:1.1
	release-2-1-0-rc2:1.1;
locks; strict;
comment	@# @;


1.1
date	2003.07.01.01.23.56;	author agmsmith;	state Exp;
branches;
next	;


desc
@@


1.1
log
@Collect a few nuggets of wisdom about how it works.
@
text
@NathanW wrote on June 30 2003:

Here's the overview:

ChainRunner:
	It's now a BLooper and it goes like this: Running the chain 
triggers an 'INIT' message, which causes it to begin to load add-ons. 
The constructor of the producer add-on calls ChainRunner's 
GetMessages() routine with a list of unique ids to fetch. It then runs 
through the list, passing in those, then calls any registered process 
callbacks after the list is exhausted. Note that finishing the list *
does not* cause the connection to be terminated and the add-ons to be 
destructed. Single pass add-ons (e.g. POP and Outbox) register a 
process callback that calls ChainRunner::Stop().

MailProtocol/MailFilter:
	No longer sets the unique id, because it's passed in. Calls 
GetMessages(), and uses ReportProgress() and ShowError() methods of 
ChainRunner instead of using the functions in status.h. Also sets SIZE 
attribute in out_headers that contains the final downloaded size of the 
message. Also now passed a ChainRunner instead of a StatusView.

That's about it, really.
-Nathan
@
