• To: "W. E. Perry" <wperry@f...>
• Subject: Re: XML, routing
• From: "J.Pietschmann" <j3322ptm@y...>
• Date: Thu, 17 Oct 2002 22:01:32 +0200
• Cc: XML DEV <xml-dev@l...>
• References: <r01050400-1021-FCCA8879E1F211D69C3D0003937A08C2@[192.168.124.21]> <3DAF0815.9E156FE2@f...>
• User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826

W. E. Perry wrote:
> So, yes, there can be value for routing in using the contents of messages to
> determine simply the network addresses to which they should be sent. Yet if
> you are doing that you are effectively only re-inventing simple network
> addressing inside the much higher (and capable of much more complex
> semantics) level of the XML document.

You wouldn't belive what set of weird requirements you
can get in the context of EDI. What about a proxy on
a firewall machine, routing XML based EDI messages to
various different machines in a network with private
IP adresses based on the messages' content?

J.Pietschmann

• References:
  • XML, routing
    • From: "Simon St.Laurent" <simonstl@s...>
  • Re: XML, routing
    • From: "W. E. Perry" <wperry@f...>

• Prev by Date: Re: fwd: metaphorical Web
• Next by Date: OASIS TC Call For Participation: e-Government TC
• Previous by thread: Perl Filter Implementation of JITTs
• Next by thread: Re: XML, routing
• Index(es):
  • Date
  • Thread