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 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 /game/{game_id} /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 entity encapsulated within0 码力 | 158 页 | 587.88 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 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 /game/{game_id} /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 entity encapsulated within0 码力 | 156 页 | 573.94 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 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 /game/{game_id} /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 entity encapsulated within0 码力 | 156 页 | 574.46 KB | 1 年前3
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”. 5.1. User Guide 21 Falcon Documentation 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 /game/{game_id} POST /game/{game_id} GameState: GET /game/{game_id}/state POST /game/{game_id}/state 5.1. User Guide 45 Falcon Documentation, Release 2.0.0 GameState may be thought of as a sub-resource of Game. It0 码力 | 184 页 | 671.87 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.0.0-b2 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 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 /game/{game_id} /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 entity encapsulated within0 码力 | 340 页 | 1.15 MB | 1 年前3
Falcon v3.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 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 /game/{game_id} /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 entity encapsulated within0 码力 | 344 页 | 1.16 MB | 1 年前3
共 36 条
- 1
- 2
- 3
- 4













