Bob Tanner wrote: > How often is the parser called? Anytime anything is loaded from disk (ie, maps, players). The maps is the big one. If the loader takes a long time, the game freezes for everyone, which would not be a good thing. As more people play, the more often maps will get loaded, and thus the bigger the problem. This can be fixed in ways other than a fast parser, and in fact should be at some point. There used to be a problem on some servers with the shared apartments - so many people piled so much loot into them, that loading that map took a noticable amount of time so the game froze. This bug was 'fixed' by each player getting a private apartment building. But one player could still in theory cause problems by piling a lot of stuff onto their private map. But I believe you really would be talking a lot of data. > > Xerces hands the parsed data off just like flex/bison. To can use callbacks to > plug in handler routines. So, it be be presented any way you want. Ok. Unclear if that will really make it save much space code then, but I'd have to look at xerces further to see how well it integrates in. Can you provide an example of an arch you've converted to xml? That may provide input as to whether pepole really want to use it or not when they see what advantages or disadvantages it may have.