Re: iSCSI: Text/Operational keys: booleans and ranges

[Paul Koning <ni1d@arrl.net>]

>>>>> "Luben" == Luben Tuikov <luben@splentec.com> writes:
 Luben> How about ranges using the dash?

 Luben> True, one could _count_ the commas to fugure out if it is a
 Luben> list (number of commas > 1) or a range (number of commas = 1),
 Luben> but you have to add code to _count_ the commas.

That doesn't work, because sets can have two members.  So yes, a
separator different from comma makes sense for ranges.

 Luben> Using a dash for ranges, the list of numerical values is
 Luben> handled by default by the already existing code in your
 Luben> implementation to intesect two strings of comma separated
 Luben> objects.

Not true.  Integers and strings are different data types.  Sets of
strings are in the spec now, sets of integers are not.

I am opposed to changes that do not come with strong justifications
(such as "this change is needed to fix bug XYZ").  I don't see any
justification for sets of integers, so they should not be added until
and unless they are needed.

    paul