XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
RE: [xml-dev] Nested Documents (was: XML 2.0)

Ok, I understand your point now.  Thanks.

Matt


-----Original Message-----
From: Michael Kay [mailto:mike@saxonica.com] 
Sent: Friday, February 29, 2008 2:20 PM
To: Johnson, Matthew C. (LNG-ALB); xml-dev@lists.xml.org
Subject: RE: [xml-dev] Nested Documents (was: XML 2.0)

> The logfile use case is a great one.  But I would be pretty 
> upset if a hospital record got dropped.  Or in the 
> environment I work in, it would not be a good thing if I 
> couldn't guarantee that a caselaw document didn't get 
> dropped.  I don't know the actual likelihood that the network 
> would fail right in between two root elements but it's a 
> situation that should be considered...shouldn't it?

The point I've been trying to make is that if your transport is so
unreliable that you need to add redundancy at the application level,
then
you ought to be using something better than this.

Michael Kay
http://www.saxonica.com/



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


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

Copyright 1993-2007 XML.org. This site is hosted by OASIS