<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>mikermcneil</author><text>Hey Peter-- RESTful endpoints are supported.  The other options are just there for convenience while testing.  You can disable those routes later if you like in your routing table.  Policy mapping happens at a controller level to solve this very problem and prevent devs from inadvertently granting access to a piece of code they didn&apos;t mean to.&lt;p&gt;# List of all users
&lt;a href=&quot;http://localhost:1337/user&quot; rel=&quot;nofollow&quot;&gt;http://localhost:1337/user&lt;/a&gt;&lt;p&gt;# Find the user with id 1
&lt;a href=&quot;http://localhost:1337/user/1&quot; rel=&quot;nofollow&quot;&gt;http://localhost:1337/user/1&lt;/a&gt;&lt;p&gt;# Create a new user
&lt;a href=&quot;http://localhost:1337/user/create?name=Fisslewick&quot; rel=&quot;nofollow&quot;&gt;http://localhost:1337/user/create?name=Fisslewick&lt;/a&gt;
(or send an HTTP POST to &lt;a href=&quot;http://localhost:1337/user&quot; rel=&quot;nofollow&quot;&gt;http://localhost:1337/user&lt;/a&gt;)&lt;p&gt;# Update the name of the user with id 1
&lt;a href=&quot;http://localhost:1337/user/update/1?name=Gordo&quot; rel=&quot;nofollow&quot;&gt;http://localhost:1337/user/update/1?name=Gordo&lt;/a&gt;
(or send an HTTP PUT to &lt;a href=&quot;http://localhost:1337/user/1&quot; rel=&quot;nofollow&quot;&gt;http://localhost:1337/user/1&lt;/a&gt;)&lt;p&gt;# Destroy the user with id 1
&lt;a href=&quot;http://localhost:1337/user/destroy/1&quot; rel=&quot;nofollow&quot;&gt;http://localhost:1337/user/destroy/1&lt;/a&gt;
(or send an HTTP DELETE to &lt;a href=&quot;http://localhost:1337/user/1&quot; rel=&quot;nofollow&quot;&gt;http://localhost:1337/user/1&lt;/a&gt;)</text><parent_chain><item><author>peter_l_downs</author><text>This looks great! The automatic API generation is a killer feature that makes me want to try this out sometime soon. Only thing that seems strange to me is adding the &amp;#60;resource&amp;#62;/create, &amp;#60;resource&amp;#62;/update, and &amp;#60;resource&amp;#62;/destroy GET endpoints -- why not keep it RESTful?</text></item></parent_chain></comment><story><title>Sails.js: Realtime MVC framework for Node.js</title><url>http://balderdashy.github.com/sails/</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>jonny_eh</author><text>I can see the desire to be able to execute non-GET commands via the browser&apos;s address bar. Another way Sails could accomplish that would be to accept &quot;?method=PUT|POST|DELETE&quot; to mimic the desired HTTP method.</text><parent_chain><item><author>peter_l_downs</author><text>This looks great! The automatic API generation is a killer feature that makes me want to try this out sometime soon. Only thing that seems strange to me is adding the &amp;#60;resource&amp;#62;/create, &amp;#60;resource&amp;#62;/update, and &amp;#60;resource&amp;#62;/destroy GET endpoints -- why not keep it RESTful?</text></item></parent_chain></comment><story><title>Sails.js: Realtime MVC framework for Node.js</title><url>http://balderdashy.github.com/sails/</url></story>