MBOX-Line: From tss at iki.fi  Tue May 31 09:05:45 2011
To: imap-protocol@u.washington.edu
From: Timo Sirainen <tss@iki.fi>
Date: Fri Jun  8 12:34:46 2018
Subject: [Imap-protocol] History question.
In-Reply-To: <78614.1306856756@parc.com>
References: <4DDEA412.6030305@aol.com> <4DDEDDD6.1040507@logicprobe.org>
	<alpine.BSO.2.00.1105261628370.892@morgaine.smi.sendmail.com>
	<2CB073A1-B421-4CFB-AE30-B17005C876A0@iki.fi>
	<78614.1306856756@parc.com>
Message-ID: <521DFEC0-1333-4244-B062-D8779F6396DB@iki.fi>

On 31.5.2011, at 18.45, Bill Janssen wrote:

> Timo Sirainen <tss@iki.fi> wrote:
> 
>> IMAP over XML maybe?..)
> 
> I'm sure it had been a long week when you wrote this, Timo.
> 
> A:  IMAP over HTTP, I suppose, though, why?  But nothing is "over" XML --
> it's just a syntax.

I meant changing the IMAP syntax to XML. For example instead of:

a FETCH 2:5 (RFC822.SIZE BODY.PEEK[HEADER.FIELDS (From To)])

it could be:

<fetch tag="a" seq="2" seq2="5">
  <size/>
  <header>From</header>
  <header>To</header>
</fetch>

But that probably still wouldn't be big enough of a change.

> Microsoft SOAP, for instance, is XML-encrypted DCE
> RPC over HTTP, designed because circa 1997 people were willing to poke
> holes in their firewalls for port 80.  HTTP is the key, not XML.


Sure, running it over HTTP would probably be required too, but I think that's a smaller problem.
