[Swift-devel] First tests with swift faster

Mihael Hategan hategan at mcs.anl.gov
Wed Feb 20 22:27:56 CST 2013


On Wed, 2013-02-20 at 22:19 -0600, Michael Wilde wrote:
> > In the faster branch the sites file is parsed with a DOM parser. This
> > will allow proper validation (which I'm working on right now).
> > 
> > There will be two versions of the sites file. The default (2.0), will
> > be
> > case-sensitive and will allow app definitions in the sites file.
> >
> > The backwards compatible one (<config version="1.0">), will be case
> > insensitive. But you will need to explicitly say version="1.0" in
> > there
> > to get that.
> 
> Could we change the <config> tag to eg <pools> or <sites> for 2.0 and leave the 1.0 parsing unchanged for true backwards compatibility?

I see. So decide the version based on the root node. Makes good sense.

> 
> > This is tentative, so open to discussion.
> 
> I think better parsing (specifically to get better error messages) is a good idea. Especially to catch mis-spelled tags (or values) that are now ignored, if thats possible.

Yes. Things will be validated against a schema (if xmlns is specified).

Also the parser now complains about unrecognized tags.

> 
> I want to get to the point where most users never type XML to use Swift, and the way to that is gensites, which should be coorinated with this change.

This is an opportunity to deal with the issue. Perhaps a better
configuration format might be the better choice.

> 
> If we're to use Coasters and the providers with Swift/T we should all be thinking about how we want this to work for users.





More information about the Swift-devel mailing list