|
11 | 11 |
|
12 | 12 | APIJSON is a JSON Transmission Structure Protocol. |
13 | 13 |
|
14 | | -You can set any JSON structure and request your server, and the server will return a JSON String with the structure you had set.<br /> |
| 14 | +You can set any JSON structure and request your server, and the server will response a JSON String with the structure you had set.<br /> |
15 | 15 | You can get any data with any JSON structure by requesting server just once. It's very convenient and flexible, and does not require a special api or multiple requests.<br /> |
16 | 16 | It provides additions and deletions, fuzzy search, remote function calls and so on. And you can save duplicate data and improve transmission speed as well!<br /> |
17 | 17 |
|
@@ -302,19 +302,19 @@ Response: |
302 | 302 | -------- | ------------ | ------------ |
303 | 303 | Requirement | Client developers append key-value pairs to an url for a request in documents | Client developers append JSON to the url for their requirements |
304 | 304 | Structure | base_url/get/table_name?<br />key0=value0&key1=value1...<br /><br />Only one table_name can be contained in an URL | base_url/get/<br />{<br > TableName0:{<br > key0:value0,<br > key1:value1,<br > ...<br > },<br > TableName1:{<br > ...<br > }<br > ...<br > }<br /><br />You can add TableNames as many as you want after an URL |
305 | | - URL | Different urls for different requests. The more diffirent kinds of request, the more different urls | One url for one method(GET,POST...), most requests use the same URL of the 7 common ones |
| 305 | + URL | Different urls for different requests. The more diffirent kinds of requests, the more different urls | One url for one method(GET,POST...), most requests use the same URL of the 7 common ones |
306 | 306 | Key-Value Pair | key=value | key:value |
307 | 307 |
|
308 | 308 | <br /> |
309 | 309 |
|
310 | 310 | Server operation | Previous way | APIJSON |
311 | 311 | -------- | ------------ | ------------ |
312 | 312 | Parse and response | Get key-value pairs and query the database with them by the default way, then encapsulate a JSON, finally return the JSON to clients | Just return what Parser#parse returned |
313 | | - Way of setting JSON structure to return | Designed in servers and cannot be modified by any clients | Designed by clients and cannot be modified by servers |
| 313 | + Way of setting JSON structure of Response | Designed in servers and cannot be modified by clients | Designed by clients and cannot be modified by servers |
314 | 314 |
|
315 | 315 | <br /> |
316 | 316 |
|
317 | | - Client parse | Previous way | APIJSON |
| 317 | + Client resolve | Previous way | APIJSON |
318 | 318 | -------- | ------------ | ------------ |
319 | 319 | View structure | Search documents or view logs after responses for requests | Just view the requests, and viewing logs after responses for requests is also supported |
320 | 320 | Operate | Parse JSON String from responses | Parse with JSONResponse or use previous way |
|
0 commit comments