<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Nov 30, 2010, at 1:07 AM, David wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Menlo; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="font-family: monospace; ">Isn't there a more natural<span class="Apple-converted-space"> </span>way of doing things ?</span></span></blockquote></div><br><div>No.</div><div><br></div><div>I'm not sure what you're asking here; it seems like you've figured out the resource model. It has some rough edges, which we are trying to eventually fix (see, for example, <<a href="http://tm.tl/3621">http://tm.tl/3621</a>>). But the things you're talking about are just how it works; <<a href="http://example.com/">http://example.com/</a>> is a collection, just like <<a href="http://example.com/foo/">http://example.com/foo/</a>>, so it behaves in a consistent way.</div><div><br></div><div>(This message may be more appropriate for the twisted-web list.)</div><div><br></div></body></html>