home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!news.univie.ac.at!scsing.switch.ch!univ-lyon1.fr!ghost.dsi.unimi.it!rpi!usc!news.service.uci.edu!ucivax!gateway
- From: eskovgaa@cue.bc.ca (Erik Skovgaard)
- Subject: Re: Differences bewtween a msg switch and gateway
- Message-ID: <1470*eskovgaa@cue.bc.ca>
- In-Reply-To: <1993Jan26.083529.6706@ugle.unit.no>
- Newsgroups: comp.protocols.iso.x400
- Approved: usenet@q2.ics.uci.edu
- Lines: 31
- Date: 27 Jan 93 15:52:49 GMT
-
- I think the differences are much more distinct.
-
- A message switch will not translate the message or address. It will merely
- pass it on as fast as possible. Commercial message switches are able to
- handle incredible throughputs and are typically based on proprietary
- message formats.
-
- A gateway will typically translate:
-
- 1. the message encoding
- 2. the address(es) of recipients(s) and originator
- 3. facilities and specific features
-
- In addition, a gateway has to "talk" both communications protocols used
- on the two sides of the gateway.
-
- A gateway is very complex (it has to know both message formats intimately)
- whereas a message switch can be quite simple and typically only would
- have to know about one message format.
-
- An X.400 MTA is a message switch - except it can also add value in some
- cases.
-
- Gateways are the scourge of the industry, but they also allow implementations
- based on proprietary and de facto standards to exchange messages with other
- systems. In the ideal world every implementation would be able to speak
- a common protocol which would eliminate gateways. Alas, the world is not
- ideal and users will have to spend a lot of time managing gateways for many
- years in the future.
-
- Cheers, ....Erik.
-