Whilst looking at
http://bugzilla.ximian.com/show_bug.cgi?id=58388 i started down the path of 'i wonder if we could keep the message around in the vfolder if its busy', and came up with the following patch.
Then of course i realised 'duh that wont help, the message isn't in use, only the uid is'. Although there are related bugs like 'messages vanishes from vfolder and vanishes from popup view too' (although for some strange reason, that appears not to be the case anymore).
It could be an interesting idea, although it can't go in yet without a lot of changes.
This is because a change like this makes messages memory-persistent singleton instances rather than being loaded every time you access one. Which means any changes, like is used to generate replies and so forth would reflected in all copies, and you would also need non-const accessors for all the fields to avoid races, etc.
camel-busymessage.diff
Description: Text Data
