Re: Fetching short text snippet for mails
Bron Gondwana <[email protected]>
| Newsgroups | gmane.ietf.imapext |
|---|---|
| Message-ID | <1418331970.2414903.201842429.24482F84@webmail.messagingengine.com> |
On Fri, Dec 12, 2014, at 04:28 AM, Stuart Brandt wrote: > Inline... > > On 12/11/14 11:53 AM, Paul Smith wrote: > > does that really matter? Will it cause real problems if the client has > > cached the old snippet and doesn't refresh it? > > The real problem is an impact to the user experience. > > Setting text/plain aside because in multipart/alternative cases the > text/html part is what's most useful for snippet generation...we see all > sorts of interesting malformed HTML variants that are expected to be > handled gracefully. Generation of snippet from such cases can yield some > pretty useless snippets. When such a case is found and a workaround is > released, it would be in the user's best interest if the prior ugly > snippet were "fixed". > > When this sort of issue comes up today with client-side snippet > generation (or HTML rendering for that matter), a new app/client is > released and in some cases it's auto-updated on the user's device. In > the end, the user experience is made whole. You know what, messages don't change that often overall. I would be totally happy with the idea that every time the modseq changes, the snippet is stale and a client should refetch if it cares. The whole point is that it's a) small b) cheap for the server to deliver So it's going to cost barely anything in bandwidth or server time to resend the snippet for any message that's had a modseq bump. Bron. -- Bron Gondwana [email protected] _______________________________________________ imapext mailing list [email protected] https://www.ietf.org/mailman/listinfo/imapext