From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from orthanc.ca ([208.79.93.154]) by ewsd; Wed Feb  5 17:16:04 EST 2020
Received: from orthanc.ca (localhost [127.0.0.1])
	by orthanc.ca (OpenSMTPD) with ESMTP id 3024ae8e;
	Wed, 5 Feb 2020 14:16:03 -0800 (PST)
From: Lyndon Nerenberg <lyndon@orthanc.ca>
To: 9front@9front.org
cc: theinicke@bss-wf.de
Subject: Re: [9front] upas/fs plumb modify for self-made flag changes
In-reply-to: <5A2F5259197B1545E61A0EA7602202E3@eigenstate.org>
References: <5A2F5259197B1545E61A0EA7602202E3@eigenstate.org>
Comments: In-reply-to ori@eigenstate.org
   message dated "Tue, 04 Feb 2020 22:11:42 -0800."
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <14751.1580940963.1@orthanc.ca>
Date: Wed, 05 Feb 2020 14:16:03 -0800
Message-ID: <6f4abd898c45c7a0@orthanc.ca>
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: cloud-oriented dependency event 

ori@eigenstate.org writes:

> imap4resp0 may modfiy the flags to match what's on the
> server. I think we want the server to have the final word
> after we set the flags, so we want to set them first:

That's correct.  You have to think of an IMAP session as an
all-encompassing state machine.  Everything an IMAP client sends
to a server is merely a suggestion.  Nothing changes until the
server sends something to the client saying a change has taken
place.

E.g., the client cannot mark a message as "deleted" unless and until
the server sends it something stating the \Deleted flag has been
set on that message, no matter how many times the client has tried
setting that flag.

--lyndon