Re: Move messages while offline using registry?

[Ted Zlatanov <tzz@lifelogs.com>]

On Fri, 07 Feb 2003, kai.grossjohann@uni-duisburg.de wrote:
> Now that the registry is there, it could be used to implement moving
> messages while offline.  

As of today, I think it's ready.  More or less.

> First of all, you'd need a place to stash the to-be-moved messages.
> Maybe nndraft:moving, or something.  Secondly, you'd need a data
> structure giving, for each group, a list of msgids of messages that
> are to be moved into that group.  And the last piece in the puzzle
> is something that injects additional articles into a group, along
> the lines of `G j', perhaps.

Shouldn't be too hard.  Insert (in the global registry that's still to
come) something like this associated with the message ID:

'('queued-move-when-connected group-name)

then on startup, Gnus can scan the registry and (if connected) do the
move.

> Hm.  I wonder if it could be easier to implement a backend that
> stores messages by their message id and that maintains a mapping
> between numbers and ids.  Then the agent could be changed to use
> that backend.  Then articles could be moved while offline.  No, it
> doesn't really sound easier.  Maybe it is better to stick with the
> old article number approach.

I honestly do not know.  I would guess it's a lot of work in the
backend, though.  Maybe the registry could be used to trace a message
ID to the group and article ID it currently occupies.  That's not too
hard, though the registry hooks will have to be modified to also take
the new article ID.

Ted