We now use a structure as the bucket data rather than just a cache level

2001-07-13  Jeffrey Stedfast  <fejj@ximian.com>

	* camel-uid-cache.c (camel_uid_cache_new): We now use a structure
	as the bucket data rather than just a cache level so set the save
	state to TRUE.
	(maybe_write_uid): We only save the uid if the cache levels are
	the same *and* if the save state is TRUE.
	(free_uid): Free the state value.
	(camel_uid_cache_get_new_uids): New uids that get added to the
	cache start with a save state of FALSE.
	(camel_uid_cache_save_uid): Set the save state of the uid to
	TRUE. What should we do if the uid isn't already in the cache?
	Currently I make it add the uid, but maybe it shouldn't?

	* providers/imap/camel-imap-folder.c (imap_filter_timeout): Update
	to reflect CamelFilterDriver API changes.

	* camel-filter-driver.c (camel_filter_driver_filter_folder): Take
	a cache argument so we can tell the cache whether or not the uid
	should be saved (meaning we have successfully filtered it).

svn path=/trunk/; revision=11084

1 files changed, 1 insertions, 2 deletions

diff --git a/camel/providers/imap/camel-imap-folder.c b/camel/providers/imap/camel-imap-folder.c
index 80f12e42a6..1d119cf4d0 100644
--- a/camel/providers/imap/camel-imap-folder.c
+++ b/camel/providers/imap/camel-imap-folder.c
@@ -1677,8 +1677,7 @@ imap_filter_timeout (gpointer user_data)
 						  "incoming", &ex);
 
 	if (driver) {
-		camel_filter_driver_filter_folder (driver, 
-						   ftd->folder, 
+		camel_filter_driver_filter_folder (driver, ftd->folder, NULL,
 						   ftd->recents, FALSE, &ex);
 
 		if (camel_exception_is_set (&ex))