Use fewer attachment-related loaders
Pare down loader complexity by processing attachment updates in
one batch for each message. Now, the list of attachments doesn't
blow away all children on every list update, and each row's view
refreshes only the properties that changed. So update processing
overhead from batching them up is minimal.
Too many loaders would have led to more headaches as message
views were recycled and all those loaders would need to be
destroyed. We do still need to destroy the one attachment list
loader, though.
Change-Id: I28b24efa61d62ed366300b970bf8f9bed4f88ab5
2 files changed