OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: [xml-dev] XML Router ?

[ Lists Home | Date Index | Thread Index ]

Rahul wrote:
> I am wondering if "XML Router" is the next big product
> in the XML space following XML accelerators and XML
> security gateways.
	If by an "XML Router" you mean a engine that can take a stream
of XML objects and, based on persistent routing rules, direct the flow
of those objects to one or more destinations, then you'll find that
much of the "Publish and Subscribe" work can be applied to the XML
routing problem. i.e. and "XML Router" is often a Publish/Subscribe
system that works on messages encoded in XML. 
	I believe that PubSub.com offers the highest horsepower "XML
Router" available for general use on the Internet today. Although we
currently only support XML streams that originate from RSS/RDF/Atom
feeds, newsgroup postings, or SEC Edgar filings, our matching engine
is completely general and can provide "routing" support for any stream
of XML objects that can be described using either XML Schema or ASN.1.
In the future, we will be providing support for other "schemas" in
addition to those we currently support.
	It is important to recognize that the "XML Router" term gets
used in a number of often confusing ways. For instance, much of the
"XML Routing" that gets done in Web Services is very like "routing" in
DNS. i.e. a message is being sent to a logical destination and the
"XML Router" looks at the logical destination information in order to
route the SOAP object to an appropriate physical resource or server.
In another usage, "XML Router" refers to a system that contains a
filtering or matching engine that does "content based" routing by
matching constraints against the detailed content of the XML object.
(i.e. deliver to XXXX if field1="foo" and field2 ="bar"). In the
former scenario, the destination of the object is "know" to its
originator, in the latter scenario, the destinations are
self-selecting -- often without the knowledge of the originators or
publishers. It should also be noted that implementing the first
scenario is massively easier than doing the second... Anyway, be aware
that "XML Router" means different things to different people.

		bob wyman
		CTO, PubSub Concepts, Inc.

  • References:


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS