2.3exp: expire and tradspool

[Katsuhiro Kondou]

In article <m11I3kt-000FaBC at independence.ecn.ou.edu>,
	Richard Michael Todd <rmtodd at mailhost.ecn.ou.edu> wrote;

} end up in the same directory tree, so the notion of 'storage class' doesn't
} really make sense here.

I think we can get the class for articles with a routine
like SMstore() does.  This can be used at tradspool_next().
I'm going to modify the code after overview code is mostly
stable and NEWNEWS is available again.

}  a) whether this would be an acceptable limitation or
}  b) whether they can think of a scheme for per-group expire that would be
} decently  efficient, and *doesn't* have that limitation.

I'm thinking of another approach:

- expireover reads expire.ctl, determines expiration time
  with Xref, and write token to a file if it should be
  expired
- sort that file and do SMcancel with those tokens
- expire just checks with SMretrieve(RETR_STAT)

btw, expireover takes much longer time if most of articles
are spooled into timecaf.  I know why it does;
SMretrieve(RETR_STAT) needs to open caf file even if it
just checks the existense.  Any resolution?
-- 
Katsuhiro Kondou