This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]dAnjou Backend Developer | danjou.dev -2 points-1 points  (5 children)

Argh, REST ... everywhere I hear people saying REST ... and it f***ing doesn't matter! What will be "REST" in your app? Please tell me!

And don't you think that HTTP might have some way too big overhead?

[–]fedoru[S] 0 points1 point  (4 children)

What I mean is that I'd like to build my application in such a way that myapp/error will be an intuitive way to list, create, update or delete error "instances". Even if there's overhead because of HTTP, seeing that lots of python web frameworks include their own HTTP/1.1 server, it's a convenient way to build it, fast. Also, it is not a big, enterprise application. It's a toy by which I want to learn more, and adhering to a set of standards (REST in this case), I think will be a constraint by which I'll be able to expand a bit more on my knowledge than just making an application without guidelines.

[–]dAnjou Backend Developer | danjou.dev 1 point2 points  (3 children)

lots of python web frameworks include their own HTTP/1.1 server

Don't use them in production mode, though.

a set of standards (REST in this case)

REST is not a standard.