Beyond 10,000 Lines: Lessons Learned from a Large Phoenix Project

Re:Beyond 10,000 Lines: Lessons Learned from a Large Phoenix... by Arcaire on Wednesday November 09, 2016 @07:22PM (#12916389)

The idea is to limit exposed routes to the standard CRUD routes: create (/new), read (/show), update (/edit), delete (/destroy).

[ Parent | on HN ]

Re:Beyond 10,000 Lines: Lessons Learned from a Large Phoenix... by nardi on Wednesday November 09, 2016 @09:24PM (#12917171)

Ugh, no. The idea is to use standard HTTP verbs (GET, POST, PUT, DELETE) with noun routes, like:

    Create: POST /resources (or PUT /resources/42)  
    Read: GET /resources/42  
    Update: PUT /resources/42 (or PATCH /resources/42)  
    Delete: DELETE /resources/42
    List/Search: GET /resources

[ Parent | on HN ]

Re:Beyond 10,000 Lines: Lessons Learned from a Large Phoenix... by aikah on Wednesday November 09, 2016 @07:32PM (#12916467)

I thought the idea was to make an API behave like a webpage by using hyperlinks that represents the state of the application, so in theory a "smart" client could navigate an API autonomously like a human interacts with a web page ? Because otherwise it's no different from RPC.

[ Parent | on HN ]

Re:Beyond 10,000 Lines: Lessons Learned from a Large Phoenix... by anthonybullard on Wednesday November 09, 2016 @08:25PM (#12916815)

I think you are thinking of HATEOAS. Read about it here: https://en.wikipedia.org/wiki/HATEOAS?wprov=sfla1

[ Parent | on HN ]