-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Choose URLs #108
Comments
I don't really like the /do part. It is really just something short I used to proxy to the back-end. I would like the following URLs to respond to GET requests:
And the following URLs to respond to POST requests
And the following URLs to respond to OPTIONS requests
|
Maybe replace /do with /object ? So the full url would be: http://review.steamedpears.com/object/new/code or http://review.steamedpears.com/object/code/unique-universal-identifier |
From our discussion before the shit fest that was last Thriday: We agreed /api/ is better than /object/ For getting content: For adding content:
|
Just to clarify, I suggest we get from |
+1 for |
Alright. I like that it's explicit. I prefer |
Also, I think of new as a verb. |
|
On Wed, 2013-04-03 at 14:37 -0700, Simon David Pratt wrote:
|
I like |
I like it better because it's as if "new" is the ID; it's just a magical ID that redirects the POST to a new ID. |
In #102, we started discussing what form the
/do
URLs should have.The text was updated successfully, but these errors were encountered: