MBOX-Line: From blong at google.com  Mon Nov 26 16:41:34 2012
To: imap-protocol@u.washington.edu
From: Brandon Long <blong@google.com>
Date: Fri Jun  8 12:34:49 2018
Subject: [Imap-protocol] Re: Suspend/Restore feature proposal
In-Reply-To: <20121126173224.Horde.BbqbGly8D0JG4aqG7fxoMw1@bigworm.curecanti.org>
References: <20121115215854.Horde.zz6B0O0tmt3ylHiEXzXhQQ4@bigworm.curecanti.org>
	<CABa8R6tHP2My0k2LqT1RzHoLQZA+X_jwUMU0cydm2sAwo8f4Fg@mail.gmail.com>
	<20121116143137.Horde.7Kb3aEW5DhM6CnuA2hAx4Q8@bigworm.curecanti.org>
	<e122fa25-9110-4b36-855d-0e7e273c5805@flaska.net>
	<20121121155417.Horde.ZeW7JqTPNxTAI-hTtrAT-Q9@bigworm.curecanti.org>
	<68035860-387d-43a9-8bb7-00744a7868b9@flaska.net>
	<20121126173224.Horde.BbqbGly8D0JG4aqG7fxoMw1@bigworm.curecanti.org>
Message-ID: <CABa8R6vCJJ_oQqiMW2Ofqu1Se-hm+h8dYx7DN6qDVT4so2mDtg@mail.gmail.com>

On Mon, Nov 26, 2012 at 4:32 PM, Michael M Slusarz <slusarz@curecanti.org>wrote:
>
>
> Because there's still no guarantee it's the same server/connection: that
> is the key to all of this.  A server can "look" the same but that doesn't
> proves anything.
>
> What happens when the server is upgraded and UTF-8 searching now works?
>  The CAPABILITY string is exactly the same.  But UTF-8 has been marked as a
> bad charset so it will still not be available.  And what about those
> commands that have been determined to be broken previously in the session?
>  It is reasonable to expect the CAPABILITY string to be the same between
> point releases of an IMAP server, but the server may have fixed the bug
> that was causing bad command behavior.


So, you deduce bugs in the server and then remember them... and this is
better than violating the ID spec?

Your adherence is commendable.

Brandon
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman13.u.washington.edu/pipermail/imap-protocol/attachments/20121126/f8fd7f84/attachment.html>
