From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Thread: 103376,7b97e385047500eb
X-Google-Attributes: gid103376,public
X-Google-Language: ENGLISH,ASCII
Path: 
 g2news1.google.com!news4.google.com!news.glorb.com!news.agarik.com!usenet-fr.net!proxad.net!infeed-2.proxad.net!news3-e.free.fr!not-for-mail
Date: Thu, 09 Dec 2004 22:04:52 +0100
From: Lionel Draghi <Lionel.nospam.Draghi@Ada-France.org>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr-FR;
 rv:1.7.3) Gecko/20041007 Debian/1.7.3-5
X-Accept-Language: fr-fr, en-us
MIME-Version: 1.0
Newsgroups: comp.lang.ada
Subject: Re: Experiences of XML parser generators for Ada?
References: <mailman.171.1102192671.10401.comp.lang.ada@ada-france.org>
 <41b23f73$0$25049$ba620e4c@news.skynet.be>
 <41b79025$0$1333$636a15ce@news.free.fr> <cp9gfv$jjb$3@a1-hrz.uni-duisburg.de>
In-Reply-To: <cp9gfv$jjb$3@a1-hrz.uni-duisburg.de>
X-Enigmail-Version: 0.89.0.0
X-Enigmail-Supports: pgp-inline, pgp-mime
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 8bit
Message-ID: <41b8be01$0$12609$626a14ce@news.free.fr>
Organization: Guest of ProXad - France
NNTP-Posting-Date: 09 Dec 2004 22:05:05 MET
NNTP-Posting-Host: 82.65.124.16
X-Trace: 1102626305 news3-e.free.fr 12609 82.65.124.16:32990
X-Complaints-To: abuse@proxad.net
Xref: g2news1.google.com comp.lang.ada:6869
Date: 2004-12-09T22:05:05+01:00
List-Id: <comp.lang.ada>

Georg Bauhaus a �crit :
...
> This problem has been discussed during XML Schema design.
> In XML Schema you have some form of ranges in the type libraries.

...

OK, thank you Georg.


> : I don't want client to continuously cause exceptions in my server, just 
> : because there is no way to let them know about the limits.
> 
> Use 'Valid and so on. Web services or not, I/O is always a possible
> source of surprises. :-)  A secure server cannot rely on external input
> anyway, I'd guess.

Clearly (although I also guess that most of the users will try to use 
the service, not to break it!)

But on the client side, I feel unconfortable not having those informations.
Let's look at the WSDL example in AWS documentation : the example uses a 
(real) service giving book prices.
The returned price is a Float. Should I expect 10 ** 59 dollars for a 
book? or 10 ** -13?

That's not a big problem, and I can understand that there is a deal 
between simplicity and power.
It's just that I feel better with
type Book_Price is delta 0.01 range 0 .. 1_000;

-- 
Lionel