Re: mail-sources backend specific?

[Lars Magne Ingebrigtsen <larsi@gnus.org>]

prj@po.cwru.edu (Paul Jarc) writes:

> The current implementation gets its efficiency by passing a list of
> groups to the backend function.  The backend then adds the article to
> all of those groups; this can use hard linking or any other speedups
> appropriate for the backend in question.

Well, the main speed-up is that since the backend controls the
splitting, it knows what it can cache and what it can't.  For
instance, nnml splitting only writes the .overview files once, no
matter how many articles arrive to each group.

But, as you say, you may do it the other way around -- do all the
splitting, and then feed a list of (say) buffer/group names to a new
backend function that puts all those buffers in all those groups.
(And sort the thing by backend, so that backend X gets all its
articles, then backend Y, etc.)

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen