Softlinks Across Outgoing Message Stores Necessary?

It might be important for IM2000 to offer the ability for senders to
transfer their messages from one store to another, notifying
recipients accordingly, so they can update their pointers.

But since not all recipients can be reliably notified of such a change
(due to network outages, and probably just not wanting to use a
heavyweight mechanism such as queued notifications for each recipient
to accomplish this), it might be necessary for senders to be able to
replace a message in a store with a link to its location in another
store.

That way, senders with access to multiple outgoing message stores will
be able to make post-injection decisions regarding which stores they'd
like to host which messages.

For example, paying to store a message in a high-availability,
highly-desirable store might be worthwhile for the first week or so
after it's sent, but, after that, maybe the sender wants the message
to continue to be available, but in a lower-availability, lower-cost
store.

Being able to put a link in the original store to where the message
exists in the new store would be helpful.

(I think it'd be best if *readers*, rather than *stores*, recursively
followed such links.  Stores should serve messages and links stored
only on them, not messages stored on other stores, even if their own
messages link to them.)

-- 
James Craig Burley
Software Craftsperson
<http://www.jcb-sc.com>