On 7 October 2011 23:09, Donald Whytock <dwhyt...@gmail.com> wrote:
> On Fri, Oct 7, 2011 at 5:10 PM, sebb <seb...@gmail.com> wrote:
>> However I think it would make sense to sort the entries by podling
>> name, rather than by name within status.
>> Otherwise it will be a pain when the status changes.
>>
>> Also, rather than use a <website> tag, I think it would be better to
>> use a tag which is the podling identity name (or whatever we call it).
>> For most podlings, this is just the name in lower-case, however there
>> are some exceptions that currently have to be hard-coded in clutch.py.
>> It's then easier to use the value to create the website and in other cases.
>
> Okay, so sorted by podling name, and instead of a website you'd like
> an "id" field that URLs and the like would be generated from? I can
> kick that out this evening.
I'm now thinking it might be better to convert some of the tags to
attributes, for example:
<podling name="Accumulo" resource="accumulo" status="current">
These are all relatively short fields and I think it would make the
file shorter and easier to read.
I used "resource" rather than "id" because that seems to be what clutch uses.
Also, XML editors / IDEs as Eclipse can show the attributes in the
outline, which makes it much easier to navigate the file
> Would it be desirable for this to be in a database? Does Infra run a
> DBMS? Either way, we can start with the XML.
Start with XML.
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
