Subj : Re: linked To : Bob Short From : Jasen Betts Date : Wed Dec 18 2002 10:07 pm Hi Bob. 17-Dec-02 10:30:07, Bob Short wrote to Jasen Betts BS> On 14 Dec 02 19:26:21, Jasen Betts said the following to Bob BS> Short: JB>> open source stuff is easily to deal with, but even closed source JB>> stuff can be "destruction tested" with artificial scenariaos. BS> But unnecessesary. The fields for POTS entries is fine. huh??? I'm talking software, you seem to be discussing file formats? JB>> nets with 10000 nodes, nodelist lines longer than the available JB>> memory, that sort of stuff :) BS> We only WISH we had that many node in a new. 2:5020 is pretty big (1423 nodes) and that breaks some software. 10000 is not IMO radically larger, BS> The rest is insignificant when using newer SW to read/write the info. nope. it shows that the programmer wasn't following the specification. stuff shopuld be tested so it can be fixed before it gets abandoned. JB>> personally I don't feel XML is the answer at the moment I lean JB>> more towards a lightweight structuered list BS> Restructured, and it may be that an ESLNL would be a bit larger. I figure about 5% before compression, mybe a little more once people start listing multiple connections, and using fields like "system name" for their original purpose once again. BS> It will require a short enrty for the POTS 1/2, and the expanded BS> enrty for the IP section... huh? half... there is no pots half. pots is optional as is IP. RS> though it will allow merging of data BS> currently spread over several enrties into a single one (multiple BS> connectivity). yeah, sosmthing that a new nodelist format should provide. JB>> one format dreamt up by Frank Vest an I went like this: BS> Except that this concept would require rearranging the POTS BS> listings too, thus making people change SW to read it. yes, or run a converter, preferably one tuned to their software type. IE ione for current POTS software and a different one for current IP software BS> But if that format is used in the IP section... I'm not shre what youre proposing there... is it a segregated nodelist (all posts info then all extended info) or multi-line (lie ESLF) if the former it'd be easier to just convert the new format for legacy software and use the new format for new software, if the latter, you'd still need a converter for existing IP software or maybe you'd need redundant data.... -=> Bye <=- --- * Origin: Success is a journey, not a destination. (3:640/1042) .