<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2912" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=165564816-06072006><FONT face=Arial
color=#0000ff size=2>good then - so I think we don't invest any
further effort on thinking about or handling this case until a
legit need to handle finer-grained associations between config settings and
directory areas arises. As long as we're reasonably convinced that we
*could* do so without causing breakage to existing usage - defer until
needed!</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=165564816-06072006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=165564816-06072006><FONT face=Arial
color=#0000ff size=2>YAGNI!</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=165564816-06072006><FONT face=Arial
color=#0000ff size=2> <A
href="http://xp.c2.com/YouArentGonnaNeedIt.html">http://xp.c2.com/YouArentGonnaNeedIt.html</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=165564816-06072006><FONT face=Arial
color=#0000ff size=2> <A
href="http://www.artima.com/weblogs/viewpost.jsp?thread=36529">http://www.artima.com/weblogs/viewpost.jsp?thread=36529</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=165564816-06072006><FONT face=Arial
color=#0000ff size=2> <A
href="http://en.wikipedia.org/wiki/YAGNI">http://en.wikipedia.org/wiki/YAGNI</A></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=165564816-06072006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=165564816-06072006><FONT face=Arial
color=#0000ff size=2>~ Deb</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Jeff Barczewski
[mailto:jeff.barczewski@gmail.com] <BR><B>Sent:</B> Thursday, July 06, 2006 9:09
AM<BR><B>To:</B> djlewis@acm.org;
masterview-devel@rubyforge.org<BR><B>Subject:</B> Re: configuring multiple
MIO<BR></FONT><BR></DIV>
<DIV></DIV>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="PADDING-LEFT: 1ex; MARGIN: 0pt 0pt 0pt 0.8ex; BORDER-LEFT: rgb(204,204,204) 1px solid">
<DIV>
<DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff 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 face=Arial color=#0000ff
size=2><SPAN></SPAN></FONT> </DIV></DIV></DIV></BLOCKQUOTE></DIV><BR></BODY></HTML>