Re: nnml/nnfolder marks faster

[prj@po.cwru.edu (Paul Jarc)]

Simon Josefsson <jas@extundo.com> wrote:
> prj@po.cwru.edu (Paul Jarc) writes:
>> I think (gnus-compress-sequence (gnus-uncompress-range range)) would
>> do it. How is 'seen special?
>
> It is a range instead of a list, which most other marks is.

They all look like lists of ranges to me, at least in .newsrc.eld.
Does Gnus still use uncompressed lists because there are backends that
can't handle rages yet?

> Where should the snippet you suggest be put?

In nn*-request-set-mark, you could calculate the new range, apply the
above to it, and store the result.  But it would probably be
significantly faster to just manipulate the list of ranges by looking
for adjacent/overlapping ranges, without recompressing.

> +(defconst gnus-article-unpropagated-mark-lists '(cache download unsend)
> +  "Marks that shouldn't be propagated to backends.
> +Typical marks are those that make no sense in a standalone backend,
> +such as marks that says if a article is stored in the cache or not

Better, I think:
such as a mark that says whether an article is stored in the cache

Are the unpropagatable marks stored in .newsrc.eld?  If they're always
recalculated, it seems they shouldn't be.  Otherwise it seems they
should be, but then they should also be stored in the backend.


paul