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] Why XML for Messaging?

[ Lists Home | Date Index | Thread Index ]

Hello Rick,

not an issue with documents, but it can be a very big problem with data 
where extraction may require information retrieval from houndreds, 
thousands, millions, etc of records. client server simply scales very badly.

But usually you don't download everything on the client, just a subset.
Anyway, even in a centralized architecture, only a subset of all data is
used. So, the same problem is shared by both server centric and client
centric architecture unless you try as much as possible to deal with the
smallest possible data set. Usually you download a bigger data set for
viewing and navigation and update a record at a time to minimize the
potential deadlocks. You do that in both server centric and client centric
architectures. Maybe you see something else as a problem. If so, can you
expand on what is precisely the scalability problem with client-server

we're starting to do it, but if note the cross thread on a recent ms 
patent i will probably have to go back to the drawing board on 

but yes, xml transport of data (i'd rather not call them objects) is 
working very well. the secret however is the message system, rather than 
the syntax of the message.

I would say both. I discovered that if your serialized objects includes some
reflective information, it is easier to transform them into language
specific construct, for instance: Java. By the way, one member of our team
discovered a way to dynamically create java classes using Beanshell. So
usually, java is a static language and you can't create new classes at
run-time, only before compilation. Our colleague found a clever way to do it
with beanshell. In conclusion, the content of the message can be
tremendously important for transforming the serialized objects into strongly
typed languages constructs. 

I need to look closely at MS patent. you may consider that RDF is a
primitive way to encode objects (in a frame like construct) it is prior art.
Its only that we never said they are objects just triples. If to keep the
lawer quiet we have to rename objects triple or gizmos, noproblem we will
provide a translation dictionary :-) :-)



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

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