Bug 3466 - RFE: split out opportunistic work from the current check/scan functions
Summary: RFE: split out opportunistic work from the current check/scan functions
Status: RESOLVED FIXED
Alias: None
Product: Spamassassin
Classification: Unclassified
Component: Libraries (show other bugs)
Version: SVN Trunk (Latest Devel Version)
Hardware: Other other
: P5 enhancement
Target Milestone: 3.2.0
Assignee: SpamAssassin Developer Mailing List
URL:
Whiteboard:
Keywords:
: 4002 (view as bug list)
Depends on:
Blocks: 4911
  Show dependency tree
 
Reported: 2004-06-03 23:28 UTC by Theo Van Dinter
Modified: 2008-01-02 14:44 UTC (History)
0 users


Attachment Type Modified Status Actions Submitter/CLA Status
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Theo Van Dinter 2004-06-03 23:28:01 UTC 
I was thinking today that instead of the current methodology (do a scan/check, then do the 
opportunistic calls, then return the results of the scan/check), we should split out the opportunistic 
functions so that we could do: scan/check, return results, do opportunistic calls.  potentially, for things 
like spamd, it could check to see if the opportunistic stuff is due to run, and if so, fork off a process to 
deal with it.

this would avoid having all the spamd procs locked up doing expiry for different users, and would also 
avoid having spamc timeout while waiting for the results to return.
Comment 1 Daniel Quinlan 2005-03-30 01:08:26 UTC 
move bug to Future milestone (previously set to Future -- I hope)
Comment 2 Theo Van Dinter 2006-12-24 23:48:56 UTC 
ok, I think I have a small patch which accomplishes most of this.  specifically,
do the check, return the result, and then if expiry is due go ahead and do it.

Sending        spamd/spamd.raw
Transmitting file data .
Committed revision 490114.
Comment 3 Justin Mason 2008-01-02 14:44:02 UTC 
*** Bug 4002 has been marked as a duplicate of this bug. ***