<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Hi Conrad,<div><br></div><div>I agree that the competition is slanted toward Rails--but since it is being sponsored by the Portland Ruby Brigade that seems only fair. Given the expectations of the hosts and attendees, it seemed reasonable to try to bend Seaside into that sort of application. Some of Seaside's power is that we can do URL parsing if we need to do so. If nothing else, I'd like to avoid an argument about the relative merits of RESTful URLs vs URL rewiring--particularly in this crowd. In any case, I'll probably save those features for the end and if I run out of time I'll fail that part of the test.</div><div><br></div><div>James</div><div><br><div><div>On Jul 22, 2008, at 2:34 PM, Conrad Taylor wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hi James, I would like to wish you the best of luck. Using Gemstone/S will allow you to concentrate on other parts of the example because you don't have to deal with RDBMS. Next, it seems that the competition caters more to Rails and REST if there's a firm requirement in regards to the URL. Thus, is it really necessary to parse the URL? For example, this is all the possible options for the search form:<div> <br></div><div>option A: no input text, no selection Result: all the items in the list</div><div><br></div><div>option B: input text, no selection Result: subset of all the items in the list</div><div><br></div><div> option C: no input text, a selection Result: subset of all the items in the list</div><div><br></div><div>option D: input text, a selection Result: subset of all the items in the list</div><div><br></div><div>Next, here's my translation of the last three bullet points on the contest page:</div> <div><br></div><div>/receipe/ID equals the Show link</div><div><span class="Apple-style-span" style="font-family: Verdana; line-height: 23px; ">/recipes/titles<em>/SUBSTRING</em> or /recipes?titles=<em>SUBSTRING equals one of the options above (i.e. text input and selector)</em></span><br> </div><div><span class="Apple-style-span" style="font-family: Verdana; font-style: italic; line-height: 23px;"><span class="Apple-style-span" style="font-style: normal; ">/recipes/course<em>/ID</em> or /recipes?course=<em>ID </em></span>equals one of the options above (i.e. text input and selector)<br> </span></div><div><br></div><div>In short, I'm thinking that the URL parsing is irrelevant because you're, for the most part, interacting with the form.</div><div><br></div><div>Good luck,</div><div><br></div><div> -Conrad</div></div></blockquote></div></div></body></html>