Re: EDI over http?

["Matthew James Gering" <mgering@xxxxxxxxxxxx>]

> HTTP is not a server to server protocol in the way that the POST command
is being
> used in some EDI implementations either.  
>
> IMAP4 allows submission and retrieval of messages/transactions between a
client 
> and a server...... so a two way exchange between two companies will look
like this.
>
>
>	Company1		 		Company 2
>	-----------------				------------------
> EDI Translator--imap4 client    ------->  	imap4 server--EDI Translator
> EDI Translator--imap4 server   <------- 	Imap4 client-- EDI Translator
>
> what is wrong with that?

Well, I don't really support the use of HTTP either -- but that aside, what
does IMAP4 hold over HTTP (honest question, it's been a while since I've
thoroughly read the IMAP specs).

HTTP has the advantage of already having an SSL implementation, for
encryption and authentication. Not that you could not have IMAP4/SSL, but
I've seen no current libraries that support that yet.

HTTP libraries and commercial packages with API's are much more widely
available at this time than the same that support IMAP4.

HTTP is strongly developed and supported by the W3C, whereas IMAP is still
closely tied to the University of Washington (not that I've anything
against my almamater).

HTTP/1.2 has been optimized for "internetwork" usage, whereas IMAP is
designed for local usage -- how does IMAP handle network congestion and
latency? I know POP/3 handles it very badly.

	Matt