That seems like a reasonable approach to me, assuming you configure the
routes accordingly.
Performance will be slower due to the nature of the search, but not by
much. I would suggest dropping an index onto the name field.
/people Lists existing person records
/people/new GET Shows an empty person form
POST Creates a new person record from request parameters
/people/99 Shows the person record having ID 99
/people/99/edit GET Shows a person form for the record having ID 99
POST Updates the person record having ID 99 using request
parameters
/people/99/destroy GET Redirects to /people/99/edit with a notice
that the user must click the form’s Destroy
button in order to destroy a record
POST Deletes the person record having ID 99 after
prompting the user for confirmation
Personally I hate the verb-object form and I hate the :id as an absolute.
We see in wikis and blogs the use of a name parameter
/people/jack
There are many settings where you don't want the user/hacker to step through
the numbers.
I'm a user of TWiki as a wiki and I find the
"http://twiki.org/cgi-bin/view/web/topic"
annoying. The "cgi-bin/view" is not needed, and as Nils Jonsson's article
points out, the move from view to edit is easier if the verb is a suffix.