[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: EDI over http?
< I am not sure if this went through the first time, so here it is again.
Is there any way to set this MajorDomo to REPRO messages? I reviewed its
command set and I certainly do not see it. It seems to be set at NOACK
NOREPRO (LISTSERV equivalents), which is quite annoying >
> One is through forms where a human being actually fills out or views a
In this case HTTP hasn't anything inherently to do with EDI transmission.
> towards using HTTP as an EDI file transfer protocol. The intent among
> be primarily used by two trading partners to exchange data in a
> real-time, point-to-point fashion. Advantages are obvious.
Okay, I have evidently missed the obvious then -- what are the obvious
I can think of two advantages:
* Real-Time response
I question the necessity of this. Could someone please elaborate.
* Session encryption
has security advantages over document encryption only.
And following disadvantages:
* Fault Taulerance
through the use of multiple MX records, it handles transmission to hosts
that are not immediately available, routing around network outages and
unreachable hosts, etc, etc.
SMTP can be gatewayed through Firewalls, gatewayed to other networks and/or
converted to other transport mechanisms such as X.400, etc..
SMTP is friendlier on the network than HTTP.
Denial of Service (DoS) attacks against web servers are far too trivial.
SMTP is a much more efficient protocol than HTTP, both in file transfer and