Sounds like a good approach. <br><br><div><span class="gmail_quote">On 7/6/06, <b class="gmail_sendername">Deb Lewis</b> <<a href="mailto:djlewis@acm.org">djlewis@acm.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<div><div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span>Side note: we'd briefly kicked around some
thoughts on whether it might be important to be able to specify some of the
config settings on multiple MIO trees vs. the single MIO structure that we
currently have. Was thinking about that and I'm informally convinced that
it would be fairly do-able without breaking the existing config protocol if we
ever wanted to do so. To support multiple MIO trees, existing protocol
would remain and map behind the scenes to the "primary" MIO tree, with some
additional protocol provided to allow adding and configuring options for
additional sections.</span></font></div>
<div dir="ltr" align="left"><font color="#0000ff" face="Arial" size="2"><span></span></font> </div>
</div>
</div></blockquote></div><br>