[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: Why XML for Messaging?

• To: "'Bullard, Claude L (Len)'" <len.bullard@i...>,'XML Developers List' <xml-dev@l...>
• Subject: RE: Why XML for Messaging?
• From: Didier PH Martin <martind@n...>
• Date: Fri, 03 Jun 2005 13:02:13 -0400
• Importance: Normal
• In-reply-to: <15725CF6AFE2F34DB8A5B4770B7334EE07206FDA@h...>
• Organization: netfolder
• Reply-to: martind@n...

Hi Len,

I agree that there is a high probability that in the future XML will be
replaced by something else, hopefully something better. I also hope that in
a closer future we finally get out of the dark ages and the actual mainframe
centric architecture connected to dumb terminals (something we call a
browser).

It's incredible how fast we stepped backward. The evolution of the beginning
90s, compound documents (in a single package and with in place editing) and
rich component based client-server environments disappeared; its like if
dinosaurs came back and wiped out more intelligent life forms. After all
these years I am still amazed to see how fast our software development
community can recede so fast and evolve so slowly. 

Now to everybody in this list:

Here is a use case submitted to the well thinking people of this group and
see how this could be resolved by XML and something else than XML. This is
honest; the contest is open to other solutions. This way we will be able to
compare.

You have three different systems:
a) the first one is running a language running in a JVM (most known are
Java, Python)
b) the second one is running on of the languages supported by a .net CLR
(most known are ECAMScript, C#, Visual Basic, a variant of java named J#)
c) the third one is simply a browser running both XSLT and ECMAScript.

You have a messaging system (i.e. a MOM) one publisher need to publish
content that can be consumed by a, b, and c. this has to be done with the
least amount of efforts from the developer.

Solution? Alternatives to XML?

I am listening....


Cheers
Didier PH Martin

• Follow-Ups:
  • RE: Why XML for Messaging?
    • From: "Michael Kay" <mike@s...>
  • Re: Why XML for Messaging?
    • From: David Lyon <david.lyon@c...>

• References:
  • RE: Why XML for Messaging?
    • From: "Bullard, Claude L (Len)" <len.bullard@i...>

• Prev by Date: RE: Why XML for Messaging?
• Next by Date: Re: schema-aware XML parser (java heap error)
• Previous by thread: RE: Why XML for Messaging?
• Next by thread: Re: Why XML for Messaging?
• Index(es):
  • Date
  • Thread