Mind map
Data Exchange Application
Map content
Data Exchange Application
Data Interface
- Tables
- Rows-Keys
- Columns - Values
- Cell - Values
- Headings (Top Row)
- Sample Data
- "id": 1009407, "name": "Loki", "description": ""
- Tables
Data Specifications
- Data Types
- String
- Date
- INT
- Data Types
Digital Methods of Exchanging Data
- REST
- HTTP Methods
- HTTP Requests
- POST
- Sends data to server to create/update resource
- GET
- Request data from a resource
- DELETE
- Deletes resource
- PUT
- Same as POST, but idempotent (i.e. It will not create multiple resources if sent twice)
- POST
- HTTP Error Messages
- 404 Not Found
- Resource is not found. Maybe deleted, or does not exist yet
- 200 OK
- Standard Response
- 201 Created
- Standard response when item has been successfully created
- 204 No content
- Standard response when nothing was returned
- 400 Bad Request
- Request was not processed due to syntax, excessive size or another client error
- 403 Forbidden
- Client does not have permission to access resource
- 500 Internal Server Error
- Generic response for unexpected failure with no specific reason
- 404 Not Found
- HTTP Requests
- Principles
- Uniform interface
- Ensures all resources follow the same format (i.e. All resources have an id)
- Uses standard HTTP methods
- Cachleable
- Resources are 'copies' to improve scalability
- Layered system
- Supports interlinking of resources
- Client-server
- Client uses resource ID to request
- Server responds with an API endpoint
- Stateless
- Does not need to remember previous requests
- Client manages its states/requests
- Uniform interface
- HTTP Methods
- JSON
- Syntax
- Structured in an array
- Collections of name/value pairs
- {type:value}
- Pros
- Easy to read and parse
- Supports different data types
- Used by many programming languages and browsers
- Cons
- Less secure
- Doesn't support namespace or comments
- Namespace - can be built in/hardcoded
- Comments - easy to read, so comments are irrelevant
- Syntax
- XML
- Syntax
- Based on HTML
- Tags ensure proper nesting
- Uses start and end tags
- <type>value</type>
- Cons
- Cross-browser parsing is more difficult
- More complex to write compared to JSON
- Only supports string data
- Pros
- Easy to read and parse
- More secure
- Uses a common programming structure
- Supports namespace and comments
- Syntax
- REST
Information
- Description
- Year 10 Digital Technologies Mind Map on Data Exchange Application, created by Kez C on 10/08/2021.
- Created by
- Kez C
- Views
- 1
- Rating