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

RE: Constrain the Number of Occurrences of Elements in your XM

• To: "'Greg Hunt'" <greg@f...>
• Subject: RE: Constrain the Number of Occurrences of Elements in your XML Schema
• From: "Michael Kay" <mike@s...>
• Date: Mon, 8 Aug 2005 08:35:20 +0100
• Cc: <xml-dev@l...>
• In-reply-to: <42F6B8F1.60805@f...>
• Thread-index: AcWbuubmlRrPCzqBROqwkJEljzkiEwAL9Bgg

> Michael,
> Why do you think I am talking about out of memory (OOM) errors?  I 
> haven't mentioned them.  I am more interested in managing 
> throughput. 

I haven't followed the thread closely enough to remember who said what, and
I wasn't directing comments at anyone in particular.

But someone on the thread was definitely talking about using schema
constraints to prevent requests being made on underlying layers of the
system that exceeded their capacity. I took "out of memory" errors as a
simple example of that idea.

I take your point that in transaction processing it may well be necessary to
analyze the requests being made on the system and bounce some of them (or
give them suitable scheduling priority) in order to protect system
throughput. However, I doubt that schema validation is a good way of doing
that.

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

• References:
  • Re: Constrain the Number of Occurrences of Elements inyour XML Schema
    • From: Greg Hunt <greg@f...>

• Prev by Date: XSLT unit testing from Java
• Next by Date: Re: Constrain the Number of Occurrences of Elements in your XML Schema
• Previous by thread: Re: Constrain the Number of Occurrences of Elements inyour XML Schema
• Next by thread: Re: Constrain the Number of Occurrences of Elements inyour XML Schema
• Index(es):
  • Date
  • Thread