gobo-eiffel-develop

[gobo-eiffel-develop] Fwd: Question about Gobo xml parsing library

[Eric B. <er...@go...>]

-------- Original Message --------
Subject: 	Question about Gobo xml parsing library
Date: 	Tue, 6 Sep 2011 05:40:50 -0400
From: 	<mon...@em...>
To: 	<gob...@li...>



Hi,

Sorry for the distribution of this mail, but I’ve no idea which person
should I send to.

Recently I’m get quite confused about the space normalization in Eiffel
xml parsing library.

I’m using nenie_mods and neniexml-01 library to parse xml, and I find
the spaces inside an attribute value will be collapsed, and the leading
and trailing spaces be discarded.

It seems that this behavior exactly conforms with the “Attribute-Value
Normalization” section in XML 1.0.

However, other xml parsing libaray, like Xerces C++ and JAXB, preserve
the spaces.

Also, when searched on Internet, I got this diff file applied to file
xm_eiffel_scanner.l:

http://gobo-eiffel.git.sourceforge.net/git/gitweb.cgi?p=gobo-eiffel/gobo;a=commitdiff;h=374c3367994f573e2699e9df7ccb9e9372196097

My question is, which behavior is the right one? And why Xerces C++,
JAXB, and the patched gobo xml library don’t conform with XML 1.0?

Thank you very much!

Regards,

Wang, Monica

Shanghai China

Telephone: 86 021 60951100 2243

Re: [gobo-eiffel-develop] Fwd: Question about Gobo xml parsing library

[Alexander K. <kw...@ah...>]

My feeling is that the processing expectations depend on whether the XML
parser is validating or not. The rule that prevents the parser from attribute
normalization is

    All attributes for which no declaration has been read SHOULD be treated
    by a non-validating processor as if declared CDATA.

And if attribute declarations are present we have

    If the attribute type is not CDATA, then the XML processor MUST further
    [collapse white spaces].

So, a non-validating XML parser should not collapse the white space
characters, while the behaviour of the validating one depends on the
associated attribute declaration.

Regards,
Alexander Kogtenkov


----- Original Message ----- 
From: "Eric Bezault" <er...@go...>
To: "Gobo Developers Mailing List" <gob...@li...>
Sent: Wednesday, September 07, 2011 12:34 AM
Subject: [gobo-eiffel-develop] Fwd: Question about Gobo xml parsing library




-------- Original Message --------
Subject: Question about Gobo xml parsing library
Date: Tue, 6 Sep 2011 05:40:50 -0400
From: <mon...@em...>
To: <gob...@li...>



Hi,

Sorry for the distribution of this mail, but I’ve no idea which person
should I send to.

Recently I’m get quite confused about the space normalization in Eiffel
xml parsing library.

I’m using nenie_mods and neniexml-01 library to parse xml, and I find
the spaces inside an attribute value will be collapsed, and the leading
and trailing spaces be discarded.

It seems that this behavior exactly conforms with the “Attribute-Value
Normalization” section in XML 1.0.

However, other xml parsing libaray, like Xerces C++ and JAXB, preserve
the spaces.

Also, when searched on Internet, I got this diff file applied to file
xm_eiffel_scanner.l:

http://gobo-eiffel.git.sourceforge.net/git/gitweb.cgi?p=gobo-eiffel/gobo;a=commitdiff;h=374c3367994f573e2699e9df7ccb9e9372196097

My question is, which behavior is the right one? And why Xerces C++,
JAXB, and the patched gobo xml library don’t conform with XML 1.0?

Thank you very much!

Regards,

Wang, Monica

Shanghai China

Telephone: 86 021 60951100 2243 

Re: [gobo-eiffel-develop] Fwd: Question about Gobo xml parsing library

[Colin P. A. <co...@co...>]

>>>>> "Alexander" == Alexander Kogtenkov <kw...@ah...> writes:

    Alexander> My feeling is that the processing expectations depend on
    Alexander> whether the XML parser is validating or not. The rule
    Alexander> that prevents the parser from attribute normalization is

    Alexander>     All attributes for which no declaration has been read
    Alexander> SHOULD be treated by a non-validating processor as if
    Alexander> declared CDATA.

    Alexander> And if attribute declarations are present we have

    Alexander>     If the attribute type is not CDATA, then the XML
    Alexander> processor MUST further [collapse white spaces].

    Alexander> So, a non-validating XML parser should not collapse the
    Alexander> white space characters, while the behaviour of the
    Alexander> validating one depends on the associated attribute
    Alexander> declaration.

And to spell it out, the Gobo XML parser is non-validating.
-- 
Colin Adams
Preston Lancashire
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

Re: [gobo-eiffel-develop] Fwd: Question about Gobo xml parsing library

[<mon...@em...>]

Thank you Alexander and Collin!

My xml document is quite simple( prolog and main node ), with no DTD or CDATA.
That means the spaces in attributes' value should always be preserved, no matter the parser is validating or not.

It seems that Nenie xml parser should be corrected (it collapses the spaces and remove leading and tailing spaces unexpectedly.)
I intend to patch Nenie xml parser with the diff I find in 
gobo-eiffel.git.sourceforge.net/git/gitweb.cgi?p=gobo-eiffel/gobo;a=commitdiff;h=374c3367994f573e2699e9df7ccb9e9372196097

But that one is for gobo xml parser, although I find the code is almost the same with Nenie xml parser.
Do you know the history between these two parsers? 
And what's the better choice for me, patch Nenie xml parser, or replace the Nenie with gobo xml parser?

Thank you in advance.



-----Original Message-----
From: Colin Paul Adams [mailto:co...@co...] 
Sent: Wednesday, September 07, 2011 12:55 PM
To: gob...@li...
Subject: Re: [gobo-eiffel-develop] Fwd: Question about Gobo xml parsing library

>>>>> "Alexander" == Alexander Kogtenkov <kw...@ah...> writes:

    Alexander> My feeling is that the processing expectations depend on
    Alexander> whether the XML parser is validating or not. The rule
    Alexander> that prevents the parser from attribute normalization is

    Alexander>     All attributes for which no declaration has been read
    Alexander> SHOULD be treated by a non-validating processor as if
    Alexander> declared CDATA.

    Alexander> And if attribute declarations are present we have

    Alexander>     If the attribute type is not CDATA, then the XML
    Alexander> processor MUST further [collapse white spaces].

    Alexander> So, a non-validating XML parser should not collapse the
    Alexander> white space characters, while the behaviour of the
    Alexander> validating one depends on the associated attribute
    Alexander> declaration.

And to spell it out, the Gobo XML parser is non-validating.
-- 
Colin Adams
Preston Lancashire
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org   - against proprietary attachments

------------------------------------------------------------------------------
Using storage to extend the benefits of virtualization and iSCSI
Virtualization increases hardware utilization and delivers a new level of
agility. Learn what those decisions are and how to modernize your storage 
and backup environments for virtualization.
http://www.accelacomm.com/jaw/sfnl/114/51434361/
_______________________________________________
gobo-eiffel-develop mailing list
gob...@li...
https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop

Re: [gobo-eiffel-develop] Fwd: Question about Gobo xml parsing library

[Colin A. <col...@gm...>]

Eric can correct me if I'm wrong, but Nenie was Franck Arnaud's
domain/library, and Franck was the most recent maintainer of the Gobo XML
parser, so you should use the Gobo parser which has many updates. It should
fully comply with XML 1.0 edition 2 (or edition 3 or edition 4, but not
edition 5, which was the W3C's way of breaking with backwards-compatibility
without incrementing the version number of XML - i.e. it should have been
XML 1.2).

On 7 September 2011 08:47, <mon...@em...> wrote:

> Thank you Alexander and Collin!
>
> My xml document is quite simple( prolog and main node ), with no DTD or
> CDATA.
> That means the spaces in attributes' value should always be preserved, no
> matter the parser is validating or not.
>
> It seems that Nenie xml parser should be corrected (it collapses the spaces
> and remove leading and tailing spaces unexpectedly.)
> I intend to patch Nenie xml parser with the diff I find in
>
> gobo-eiffel.git.sourceforge.net/git/gitweb.cgi?p=gobo-eiffel/gobo;a=commitdiff;h=374c3367994f573e2699e9df7ccb9e9372196097
>
> But that one is for gobo xml parser, although I find the code is almost the
> same with Nenie xml parser.
> Do you know the history between these two parsers?
> And what's the better choice for me, patch Nenie xml parser, or replace the
> Nenie with gobo xml parser?
>
> Thank you in advance.
>
>
>
> -----Original Message-----
> From: Colin Paul Adams [mailto:co...@co...]
> Sent: Wednesday, September 07, 2011 12:55 PM
> To: gob...@li...
> Subject: Re: [gobo-eiffel-develop] Fwd: Question about Gobo xml parsing
> library
>
> >>>>> "Alexander" == Alexander Kogtenkov <kw...@ah...> writes:
>
>    Alexander> My feeling is that the processing expectations depend on
>    Alexander> whether the XML parser is validating or not. The rule
>    Alexander> that prevents the parser from attribute normalization is
>
>    Alexander>     All attributes for which no declaration has been read
>    Alexander> SHOULD be treated by a non-validating processor as if
>    Alexander> declared CDATA.
>
>    Alexander> And if attribute declarations are present we have
>
>    Alexander>     If the attribute type is not CDATA, then the XML
>    Alexander> processor MUST further [collapse white spaces].
>
>    Alexander> So, a non-validating XML parser should not collapse the
>    Alexander> white space characters, while the behaviour of the
>    Alexander> validating one depends on the associated attribute
>    Alexander> declaration.
>
> And to spell it out, the Gobo XML parser is non-validating.
> --
> Colin Adams
> Preston Lancashire
> ()  ascii ribbon campaign - against html e-mail
> /\  www.asciiribbon.org   - against proprietary attachments
>
>
> ------------------------------------------------------------------------------
> Using storage to extend the benefits of virtualization and iSCSI
> Virtualization increases hardware utilization and delivers a new level of
> agility. Learn what those decisions are and how to modernize your storage
> and backup environments for virtualization.
> http://www.accelacomm.com/jaw/sfnl/114/51434361/
> _______________________________________________
> gobo-eiffel-develop mailing list
> gob...@li...
> https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop
>
>
>
> ------------------------------------------------------------------------------
> Using storage to extend the benefits of virtualization and iSCSI
> Virtualization increases hardware utilization and delivers a new level of
> agility. Learn what those decisions are and how to modernize your storage
> and backup environments for virtualization.
> http://www.accelacomm.com/jaw/sfnl/114/51434361/
> _______________________________________________
> gobo-eiffel-develop mailing list
> gob...@li...
> https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop
>

Re: [gobo-eiffel-develop] Fwd: Question about Gobo xml parsing library

[<mon...@em...>]

I c.
Thanks.

From: Colin Adams [mailto:col...@gm...]
Sent: Wednesday, September 07, 2011 3:57 PM
To: Wang, Monica
Cc: gob...@li...
Subject: Re: [gobo-eiffel-develop] Fwd: Question about Gobo xml parsing library

Eric can correct me if I'm wrong, but Nenie was Franck Arnaud's domain/library, and Franck was the most recent maintainer of the Gobo XML parser, so you should use the Gobo parser which has many updates. It should fully comply with XML 1.0 edition 2 (or edition 3 or edition 4, but not edition 5, which was the W3C's way of breaking with backwards-compatibility without incrementing the version number of XML - i.e. it should have been XML 1.2).
On 7 September 2011 08:47, <mon...@em...<mailto:mon...@em...>> wrote:
Thank you Alexander and Collin!

My xml document is quite simple( prolog and main node ), with no DTD or CDATA.
That means the spaces in attributes' value should always be preserved, no matter the parser is validating or not.

It seems that Nenie xml parser should be corrected (it collapses the spaces and remove leading and tailing spaces unexpectedly.)
I intend to patch Nenie xml parser with the diff I find in
gobo-eiffel.git.sourceforge.net/git/gitweb.cgi?p=gobo-eiffel/gobo;a=commitdiff;h=374c3367994f573e2699e9df7ccb9e9372196097<http://gobo-eiffel.git.sourceforge.net/git/gitweb.cgi?p=gobo-eiffel/gobo;a=commitdiff;h=374c3367994f573e2699e9df7ccb9e9372196097>

But that one is for gobo xml parser, although I find the code is almost the same with Nenie xml parser.
Do you know the history between these two parsers?
And what's the better choice for me, patch Nenie xml parser, or replace the Nenie with gobo xml parser?

Thank you in advance.



-----Original Message-----
From: Colin Paul Adams [mailto:co...@co...<mailto:co...@co...>]
Sent: Wednesday, September 07, 2011 12:55 PM
To: gob...@li...<mailto:gob...@li...>
Subject: Re: [gobo-eiffel-develop] Fwd: Question about Gobo xml parsing library

>>>>> "Alexander" == Alexander Kogtenkov <kw...@ah...<mailto:kw...@ah...>> writes:

   Alexander> My feeling is that the processing expectations depend on
   Alexander> whether the XML parser is validating or not. The rule
   Alexander> that prevents the parser from attribute normalization is

   Alexander>     All attributes for which no declaration has been read
   Alexander> SHOULD be treated by a non-validating processor as if
   Alexander> declared CDATA.

   Alexander> And if attribute declarations are present we have

   Alexander>     If the attribute type is not CDATA, then the XML
   Alexander> processor MUST further [collapse white spaces].

   Alexander> So, a non-validating XML parser should not collapse the
   Alexander> white space characters, while the behaviour of the
   Alexander> validating one depends on the associated attribute
   Alexander> declaration.

And to spell it out, the Gobo XML parser is non-validating.
--
Colin Adams
Preston Lancashire
()  ascii ribbon campaign - against html e-mail
/\  www.asciiribbon.org<http://www.asciiribbon.org>   - against proprietary attachments

------------------------------------------------------------------------------
Using storage to extend the benefits of virtualization and iSCSI
Virtualization increases hardware utilization and delivers a new level of
agility. Learn what those decisions are and how to modernize your storage
and backup environments for virtualization.
http://www.accelacomm.com/jaw/sfnl/114/51434361/
_______________________________________________
gobo-eiffel-develop mailing list
gob...@li...<mailto:gob...@li...>
https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop


------------------------------------------------------------------------------
Using storage to extend the benefits of virtualization and iSCSI
Virtualization increases hardware utilization and delivers a new level of
agility. Learn what those decisions are and how to modernize your storage
and backup environments for virtualization.
http://www.accelacomm.com/jaw/sfnl/114/51434361/
_______________________________________________
gobo-eiffel-develop mailing list
gob...@li...<mailto:gob...@li...>
https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop

Re: [gobo-eiffel-develop] Fwd: Question about Gobo xml parsing library

[Franck A. <fr...@ne...>]

Hi,

Yes you should use Gobo's XML library, whose code started with Nenie XML
many years ago, and Nenie XML hasn't been maintained since it moved to
Gobo. I'm almost surprised it still works at all on current compilers
after all those years :-).

I think Alexander is on the thing re the reason, I don't recall the
exact details but I had read something wrong from the standard on
normalization and fixed it once it was in Gobo (actually I think there
might be some remaining issues in that area, either of inelegant
implementation or some obscure normalisation case that you don't
actually hit in real life, or something).

Well done with the detective work btw ;-).

Cheers
Franck

On Wednesday, September 07, 2011 4:16 AM, mon...@em... wrote:
> I c.
> Thanks.
> 
> From: Colin Adams [mailto:col...@gm...]
> Sent: Wednesday, September 07, 2011 3:57 PM
> To: Wang, Monica
> Cc: gob...@li...
> Subject: Re: [gobo-eiffel-develop] Fwd: Question about Gobo xml parsing
> library
> 
> Eric can correct me if I'm wrong, but Nenie was Franck Arnaud's
> domain/library, and Franck was the most recent maintainer of the Gobo XML
> parser, so you should use the Gobo parser which has many updates. It
> should fully comply with XML 1.0 edition 2 (or edition 3 or edition 4,
> but not edition 5, which was the W3C's way of breaking with
> backwards-compatibility without incrementing the version number of XML -
> i.e. it should have been XML 1.2).
> On 7 September 2011 08:47,
> <mon...@em...<mailto:mon...@em...>> wrote:
> Thank you Alexander and Collin!
> 
> My xml document is quite simple( prolog and main node ), with no DTD or
> CDATA.
> That means the spaces in attributes' value should always be preserved, no
> matter the parser is validating or not.
> 
> It seems that Nenie xml parser should be corrected (it collapses the
> spaces and remove leading and tailing spaces unexpectedly.)
> I intend to patch Nenie xml parser with the diff I find in
> gobo-eiffel.git.sourceforge.net/git/gitweb.cgi?p=gobo-eiffel/gobo;a=commitdiff;h=374c3367994f573e2699e9df7ccb9e9372196097<http://gobo-eiffel.git.sourceforge.net/git/gitweb.cgi?p=gobo-eiffel/gobo;a=commitdiff;h=374c3367994f573e2699e9df7ccb9e9372196097>
> 
> But that one is for gobo xml parser, although I find the code is almost
> the same with Nenie xml parser.
> Do you know the history between these two parsers?
> And what's the better choice for me, patch Nenie xml parser, or replace
> the Nenie with gobo xml parser?
> 
> Thank you in advance.
> 
> 
> 
> -----Original Message-----
> From: Colin Paul Adams
> [mailto:co...@co...<mailto:co...@co...>]
> Sent: Wednesday, September 07, 2011 12:55 PM
> To:
> gob...@li...<mailto:gob...@li...>
> Subject: Re: [gobo-eiffel-develop] Fwd: Question about Gobo xml parsing
> library
> 
> >>>>> "Alexander" == Alexander Kogtenkov <kw...@ah...<mailto:kw...@ah...>> writes:
> 
>    Alexander> My feeling is that the processing expectations depend on
>    Alexander> whether the XML parser is validating or not. The rule
>    Alexander> that prevents the parser from attribute normalization is
> 
>    Alexander>     All attributes for which no declaration has been read
>    Alexander> SHOULD be treated by a non-validating processor as if
>    Alexander> declared CDATA.
> 
>    Alexander> And if attribute declarations are present we have
> 
>    Alexander>     If the attribute type is not CDATA, then the XML
>    Alexander> processor MUST further [collapse white spaces].
> 
>    Alexander> So, a non-validating XML parser should not collapse the
>    Alexander> white space characters, while the behaviour of the
>    Alexander> validating one depends on the associated attribute
>    Alexander> declaration.
> 
> And to spell it out, the Gobo XML parser is non-validating.
> --
> Colin Adams
> Preston Lancashire
> ()  ascii ribbon campaign - against html e-mail
> /\  www.asciiribbon.org<http://www.asciiribbon.org>   - against
> proprietary attachments
> 
> ------------------------------------------------------------------------------
> Using storage to extend the benefits of virtualization and iSCSI
> Virtualization increases hardware utilization and delivers a new level of
> agility. Learn what those decisions are and how to modernize your storage
> and backup environments for virtualization.
> http://www.accelacomm.com/jaw/sfnl/114/51434361/
> _______________________________________________
> gobo-eiffel-develop mailing list
> gob...@li...<mailto:gob...@li...>
> https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop
> 
> 
> ------------------------------------------------------------------------------
> Using storage to extend the benefits of virtualization and iSCSI
> Virtualization increases hardware utilization and delivers a new level of
> agility. Learn what those decisions are and how to modernize your storage
> and backup environments for virtualization.
> http://www.accelacomm.com/jaw/sfnl/114/51434361/
> _______________________________________________
> gobo-eiffel-develop mailing list
> gob...@li...<mailto:gob...@li...>
> https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop
> 
> 
> ------------------------------------------------------------------------------
> Using storage to extend the benefits of virtualization and iSCSI
> Virtualization increases hardware utilization and delivers a new level of
> agility. Learn what those decisions are and how to modernize your storage 
> and backup environments for virtualization.
> http://www.accelacomm.com/jaw/sfnl/114/51434361/
> _______________________________________________
> gobo-eiffel-develop mailing list
> gob...@li...
> https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop
> 

Re: [gobo-eiffel-develop] Fwd: Question about Gobo xml parsing library

[<mon...@em...>]

Thank you Frank. It's really helpful.

-----Original Message-----
From: Franck Arnaud [mailto:fr...@ne...] 
Sent: Wednesday, September 07, 2011 8:31 PM
To: Godo Develop
Subject: Re: [gobo-eiffel-develop] Fwd: Question about Gobo xml parsing library

Hi,

Yes you should use Gobo's XML library, whose code started with Nenie XML
many years ago, and Nenie XML hasn't been maintained since it moved to
Gobo. I'm almost surprised it still works at all on current compilers
after all those years :-).

I think Alexander is on the thing re the reason, I don't recall the
exact details but I had read something wrong from the standard on
normalization and fixed it once it was in Gobo (actually I think there
might be some remaining issues in that area, either of inelegant
implementation or some obscure normalisation case that you don't
actually hit in real life, or something).

Well done with the detective work btw ;-).

Cheers
Franck

On Wednesday, September 07, 2011 4:16 AM, mon...@em... wrote:
> I c.
> Thanks.
> 
> From: Colin Adams [mailto:col...@gm...]
> Sent: Wednesday, September 07, 2011 3:57 PM
> To: Wang, Monica
> Cc: gob...@li...
> Subject: Re: [gobo-eiffel-develop] Fwd: Question about Gobo xml parsing
> library
> 
> Eric can correct me if I'm wrong, but Nenie was Franck Arnaud's
> domain/library, and Franck was the most recent maintainer of the Gobo XML
> parser, so you should use the Gobo parser which has many updates. It
> should fully comply with XML 1.0 edition 2 (or edition 3 or edition 4,
> but not edition 5, which was the W3C's way of breaking with
> backwards-compatibility without incrementing the version number of XML -
> i.e. it should have been XML 1.2).
> On 7 September 2011 08:47,
> <mon...@em...<mailto:mon...@em...>> wrote:
> Thank you Alexander and Collin!
> 
> My xml document is quite simple( prolog and main node ), with no DTD or
> CDATA.
> That means the spaces in attributes' value should always be preserved, no
> matter the parser is validating or not.
> 
> It seems that Nenie xml parser should be corrected (it collapses the
> spaces and remove leading and tailing spaces unexpectedly.)
> I intend to patch Nenie xml parser with the diff I find in
> gobo-eiffel.git.sourceforge.net/git/gitweb.cgi?p=gobo-eiffel/gobo;a=commitdiff;h=374c3367994f573e2699e9df7ccb9e9372196097<http://gobo-eiffel.git.sourceforge.net/git/gitweb.cgi?p=gobo-eiffel/gobo;a=commitdiff;h=374c3367994f573e2699e9df7ccb9e9372196097>
> 
> But that one is for gobo xml parser, although I find the code is almost
> the same with Nenie xml parser.
> Do you know the history between these two parsers?
> And what's the better choice for me, patch Nenie xml parser, or replace
> the Nenie with gobo xml parser?
> 
> Thank you in advance.
> 
> 
> 
> -----Original Message-----
> From: Colin Paul Adams
> [mailto:co...@co...<mailto:co...@co...>]
> Sent: Wednesday, September 07, 2011 12:55 PM
> To:
> gob...@li...<mailto:gob...@li...>
> Subject: Re: [gobo-eiffel-develop] Fwd: Question about Gobo xml parsing
> library
> 
> >>>>> "Alexander" == Alexander Kogtenkov <kw...@ah...<mailto:kw...@ah...>> writes:
> 
>    Alexander> My feeling is that the processing expectations depend on
>    Alexander> whether the XML parser is validating or not. The rule
>    Alexander> that prevents the parser from attribute normalization is
> 
>    Alexander>     All attributes for which no declaration has been read
>    Alexander> SHOULD be treated by a non-validating processor as if
>    Alexander> declared CDATA.
> 
>    Alexander> And if attribute declarations are present we have
> 
>    Alexander>     If the attribute type is not CDATA, then the XML
>    Alexander> processor MUST further [collapse white spaces].
> 
>    Alexander> So, a non-validating XML parser should not collapse the
>    Alexander> white space characters, while the behaviour of the
>    Alexander> validating one depends on the associated attribute
>    Alexander> declaration.
> 
> And to spell it out, the Gobo XML parser is non-validating.
> --
> Colin Adams
> Preston Lancashire
> ()  ascii ribbon campaign - against html e-mail
> /\  www.asciiribbon.org<http://www.asciiribbon.org>   - against
> proprietary attachments
> 
> ------------------------------------------------------------------------------
> Using storage to extend the benefits of virtualization and iSCSI
> Virtualization increases hardware utilization and delivers a new level of
> agility. Learn what those decisions are and how to modernize your storage
> and backup environments for virtualization.
> http://www.accelacomm.com/jaw/sfnl/114/51434361/
> _______________________________________________
> gobo-eiffel-develop mailing list
> gob...@li...<mailto:gob...@li...>
> https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop
> 
> 
> ------------------------------------------------------------------------------
> Using storage to extend the benefits of virtualization and iSCSI
> Virtualization increases hardware utilization and delivers a new level of
> agility. Learn what those decisions are and how to modernize your storage
> and backup environments for virtualization.
> http://www.accelacomm.com/jaw/sfnl/114/51434361/
> _______________________________________________
> gobo-eiffel-develop mailing list
> gob...@li...<mailto:gob...@li...>
> https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop
> 
> 
> ------------------------------------------------------------------------------
> Using storage to extend the benefits of virtualization and iSCSI
> Virtualization increases hardware utilization and delivers a new level of
> agility. Learn what those decisions are and how to modernize your storage 
> and backup environments for virtualization.
> http://www.accelacomm.com/jaw/sfnl/114/51434361/
> _______________________________________________
> gobo-eiffel-develop mailing list
> gob...@li...
> https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop
> 

------------------------------------------------------------------------------
Using storage to extend the benefits of virtualization and iSCSI
Virtualization increases hardware utilization and delivers a new level of
agility. Learn what those decisions are and how to modernize your storage 
and backup environments for virtualization.
http://www.accelacomm.com/jaw/sfnl/114/51434361/
_______________________________________________
gobo-eiffel-develop mailing list
gob...@li...
https://lists.sourceforge.net/lists/listinfo/gobo-eiffel-develop