<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; "><DIV><DIV>On 4-Apr-07, at 11:09 AM, Eleanor wrote:</DIV><BR class="Apple-interchange-newline"><BLOCKQUOTE type="cite"><P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">This should make for an interesting discussion then as I'm pro-REST <SPAN class="Apple-converted-space"> </SPAN></FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">at the infrastructure level but see the Rails RESTful methodology as <SPAN class="Apple-converted-space"> </SPAN></FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">deeply flawed. We don't expect database application designers to <SPAN class="Apple-converted-space"> </SPAN></FONT></P> <P style="margin: 0.0px 0.0px 0.0px 0.0px"><FONT face="Helvetica" size="3" style="font: 12.0px Helvetica">limit themselves to CRUD so why should we expect Web developers?</FONT></P> </BLOCKQUOTE></DIV><BR><DIV>I tend to agree. I pondered long and hard about it and eventually decided that CRUD != REST, and in fact they both have seriously limited value, although what they do they do very well and better than any alternative. I'm looking forward to the discussion on the 16th!</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>Paul.</DIV><DIV><BR class="khtml-block-placeholder"></DIV></BODY></HTML>