Falcon v1.4.1-post-1 Documentationexample, an event booking application may have resources such as “ticket” and “venue”, while a video game backend may have resources such as “achievements” and “player”. URLs provide a way for the client schema: GET /game/ping GET /game/{game_id} POST /game/{game_id} GET /game/{game_id}/state POST /game/{game_id}/state We can break this down into three resources: Ping: GET /game/ping Game: GET GET /game/{game_id} POST /game/{game_id} GameState: GET /game/{game_id}/state POST /game/{game_id}/state GameState may be thought of as a sub-resource of Game. It is a distinct logical entity0 码力 | 229 页 | 273.39 KB | 1 年前3
Falcon v1.4.0 Documentationexample, an event booking application may have resources such as “ticket” and “venue”, while a video game backend may have resources such as “achievements” and “player”. URLs provide a way for the client schema: GET /game/ping GET /game/{game_id} POST /game/{game_id} GET /game/{game_id}/state POST /game/{game_id}/state We can break this down into three resources: Ping: GET /game/ping Game: GET GET /game/{game_id} POST /game/{game_id} GameState: GET /game/{game_id}/state POST /game/{game_id}/state GameState may be thought of as a sub-resource of Game. It is a distinct logical entity0 码力 | 230 页 | 271.65 KB | 1 年前3
Falcon v1.4.1 Documentationexample, an event booking application may have resources such as “ticket” and “venue”, while a video game backend may have resources such as “achievements” and “player”. URLs provide a way for the client schema: GET /game/ping GET /game/{game_id} POST /game/{game_id} GET /game/{game_id}/state POST /game/{game_id}/state We can break this down into three resources: Ping: GET /game/ping Game: GET GET /game/{game_id} POST /game/{game_id} GameState: GET /game/{game_id}/state POST /game/{game_id}/state GameState may be thought of as a sub-resource of Game. It is a distinct logical entity0 码力 | 231 页 | 272.52 KB | 1 年前3
Falcon v2.0.0 Documentationexample, an event booking application may have resources such as “ticket” and “venue”, while a video game backend may have resources such as “achievements” and “player”. URLs provide a way for the client schema: GET /game/ping GET /game/{game_id} POST /game/{game_id} GET /game/{game_id}/state POST /game/{game_id}/state We can break this down into three resources: Ping: GET /game/ping Game: GET GET /game/{game_id} POST /game/{game_id} GameState: GET /game/{game_id}/state POST /game/{game_id}/state GameState may be thought of as a sub-resource of Game. It is a distinct logical entity0 码力 | 265 页 | 299.57 KB | 1 年前3
Falcon v3.1.1 Documentationexample, an event booking application may have resources such as “ticket” and “venue”, while a video game backend may have resources such as “achievements” and “player”. URLs provide a way for the client schema: GET /game/ping GET /game/{game_id} POST /game/{game_id} GET /game/{game_id}/state POST /game/{game_id}/state We can break this down into three resources: Ping: GET /game/ping Game: GET GET /game/{game_id} POST /game/{game_id} GameState: GET /game/{game_id}/state POST /game/{game_id}/state GameState may be thought of as a sub-resource of Game. It is a distinct logical entity0 码力 | 540 页 | 476.60 KB | 1 年前3
Falcon v3.1.1-rc1 Documentationexample, an event booking application may have resources such as “ticket” and “venue”, while a video game backend may have resources such as “achievements” and “player”. URLs provide a way for the client schema: GET /game/ping GET /game/{game_id} POST /game/{game_id} GET /game/{game_id}/state POST /game/{game_id}/state We can break this down into three resources: Ping: GET /game/ping Game: GET GET /game/{game_id} POST /game/{game_id} GameState: GET /game/{game_id}/state POST /game/{game_id}/state GameState may be thought of as a sub-resource of Game. It is a distinct logical entity0 码力 | 540 页 | 476.61 KB | 1 年前3
Falcon v3.1.0 Documentationexample, an event booking application may have resources such as “ticket” and “venue”, while a video game backend may have resources such as “achievements” and “player”. URLs provide a way for the client schema: GET /game/ping GET /game/{game_id} POST /game/{game_id} GET /game/{game_id}/state POST /game/{game_id}/state We can break this down into three resources: Ping: GET /game/ping Game: GET GET /game/{game_id} POST /game/{game_id} GameState: GET /game/{game_id}/state POST /game/{game_id}/state GameState may be thought of as a sub-resource of Game. It is a distinct logical entity0 码力 | 537 页 | 474.34 KB | 1 年前3
Falcon v3.1.1-b3 Documentationexample, an event booking application may have resources such as “ticket” and “venue”, while a video game backend may have resources such as “achievements” and “player”. URLs provide a way for the client schema: GET /game/ping GET /game/{game_id} POST /game/{game_id} GET /game/{game_id}/state POST /game/{game_id}/state We can break this down into three resources: Ping: GET /game/ping Game: GET GET /game/{game_id} POST /game/{game_id} GameState: GET /game/{game_id}/state POST /game/{game_id}/state GameState may be thought of as a sub-resource of Game. It is a distinct logical entity0 码力 | 540 页 | 476.61 KB | 1 年前3
Falcon v3.1.1-a Documentationexample, an event booking application may have resources such as “ticket” and “venue”, while a video game backend may have resources such as “achievements” and “player”. URLs provide a way for the client schema: GET /game/ping GET /game/{game_id} POST /game/{game_id} GET /game/{game_id}/state POST /game/{game_id}/state We can break this down into three resources: Ping: GET /game/ping Game: GET GET /game/{game_id} POST /game/{game_id} GameState: GET /game/{game_id}/state POST /game/{game_id}/state GameState may be thought of as a sub-resource of Game. It is a distinct logical entity0 码力 | 540 页 | 476.60 KB | 1 年前3
Falcon v3.1.1-b1 Documentationexample, an event booking application may have resources such as “ticket” and “venue”, while a video game backend may have resources such as “achievements” and “player”. URLs provide a way for the client schema: GET /game/ping GET /game/{game_id} POST /game/{game_id} GET /game/{game_id}/state POST /game/{game_id}/state We can break this down into three resources: Ping: GET /game/ping Game: GET GET /game/{game_id} POST /game/{game_id} GameState: GET /game/{game_id}/state POST /game/{game_id}/state GameState may be thought of as a sub-resource of Game. It is a distinct logical entity0 码力 | 540 页 | 476.61 KB | 1 年前3
共 63 条
- 1
- 2
- 3
- 4
- 5
- 6
- 7













