vault backup: 2026-08-10 02:12:27
This commit is contained in:
@@ -13,7 +13,7 @@ debugInConsole: false # Print debug info in Obsidian console
|
||||
|
||||
<div class="page-break"></div>
|
||||
|
||||
# REST API General Tips
|
||||
# REST API General Tips
|
||||
|
||||
## HTTP Status Messages
|
||||
HTTP response status codes indicate whether a specific HTTP request has been successfully completed. Responses are grouped in five classes:
|
||||
@@ -26,15 +26,15 @@ HTTP response status codes indicate whether a specific HTTP request has been suc
|
||||
|
||||
Often used codes in excercises are:
|
||||
|
||||
| Code | Name | Purpose | |
|
||||
| ------- | ---------------- | --------------------------------------------------------------------------------------------------------------------- | --- |
|
||||
| **2xx** | **Successful** | | |
|
||||
| 200 | OK | The request is OK (this is the standard response for successful HTTP requests) | |
|
||||
| 201 | Created | The request has been fulfilled, and a new resource is created | |
|
||||
| 204 | No Content | The request has been successfully processed, but is not returning any content (may be returned for successful delete) | |
|
||||
| **4xx** | **Client Error** | | |
|
||||
| 400 | Bad Request | The request cannot be fulfilled due to bad syntax or content | |
|
||||
| 404 | Not Found | The requested page/resource could not be found | |
|
||||
| Code | Name | Purpose |
|
||||
| ------- | ---------------- | --------------------------------------------------------------------------------------------------------------------- |
|
||||
| **2xx** | **Successful** | |
|
||||
| 200 | OK | The request is OK (this is the standard response for successful HTTP requests) |
|
||||
| 201 | Created | The request has been fulfilled, and a new resource is created |
|
||||
| 204 | No Content | The request has been successfully processed, but is not returning any content (may be returned for successful delete) |
|
||||
| **4xx** | **Client Error** | |
|
||||
| 400 | Bad Request | The request cannot be fulfilled due to bad syntax or content |
|
||||
| 404 | Not Found | The requested page/resource could not be found |
|
||||
|
||||
If you don't know an HTTP Code you can use `HttpStatus.<Message Name>.value()` class in Java
|
||||
For example: `HttpStatus.OK.value()` returns `200`
|
||||
@@ -1247,7 +1247,7 @@ struct Shower {
|
||||
Before they can be used they also need to be initialized
|
||||
```C
|
||||
struct Shower s;;
|
||||
pthread_mutex_init(&s.showerLock,NULL); // The se
|
||||
pthread_mutex_init(&s.showerLock,NULL);
|
||||
```
|
||||
The second parameter is a mutex attribute which determines what kind of mutex it is. The kind of a mutex determines whether it can be locked again by a thread that already owns it.
|
||||
**For our purposes not specifying is okay and you can pass NULL.**
|
||||
@@ -1624,7 +1624,7 @@ Some of the most common instructions in a `Dockerfile` include:
|
||||
### Building docker
|
||||
|
||||
```bash
|
||||
docker build -t <tag>
|
||||
docker build -t <tag> .
|
||||
```
|
||||
|
||||
### Docker processes
|
||||
@@ -2118,6 +2118,11 @@ sudo alternatives --config java
|
||||
sudo alternatives --config javac
|
||||
```
|
||||
|
||||
## To cancel an automatic shutdown
|
||||
```bash
|
||||
sudo shutdown -c
|
||||
```
|
||||
|
||||
<div class="page-break"></div>
|
||||
|
||||
# ALL RESOURCE LINKS:
|
||||
@@ -2142,3 +2147,49 @@ sudo alternatives --config javac
|
||||
- **EasyMock:** https://easymock.org/user-guide.html
|
||||
- **man pages (command line, not online)**
|
||||
|
||||
# Excersises:
|
||||
- **L09P02** Garching Best Software
|
||||
- **L10PE01** Tutor Meeting Management
|
||||
- **L09P01** Registry Office Service Deployment
|
||||
- **L09PE01** TUMPixel
|
||||
- **L09PE02** Wizardry Character Creation
|
||||
- **L09PE03** Your First Kubernetes Deployment
|
||||
- **L08P01** Oops Another Git Merge Conflict
|
||||
- **L08P02** Multilingual Codebase using Bazel
|
||||
- **L08PE01** Continuous Integration
|
||||
- **L08PE02** Merge the Right Merge
|
||||
- **L08PE03** Defend FoodPalace
|
||||
- **L08PE04** Spaceship
|
||||
- **L07P01** Spot the Bugs
|
||||
- **L07P02** Dynamic Code analysis for Priority Scheduling
|
||||
- **L07PE01** The Recovery of Aniruddhs Restaurant Part 2
|
||||
- **L07PE02** Playlist Manager -- Memory Debugging with MemorySanitizer
|
||||
- **L07PE03** Gym Threading
|
||||
- **L06P01** University App Unit Testing Part 2
|
||||
- **L06P02** Discussion Forum Mock Testing
|
||||
- **L06PE01** The Iron Bank of Braavos
|
||||
- **L06PE02** Student Absences System Testing
|
||||
- **L06PE03** Tutorial Service
|
||||
- **L05P01** Database Sharding and Recovery
|
||||
- **L05P02** Searching in e-BOOKist
|
||||
- **L05P03** Old Beer Factory Digitalization
|
||||
- **L05PE01** Capability-based File Sharing
|
||||
- **L05PE02** Thermometer Adapter
|
||||
- **L05PE03** Observer Pattern
|
||||
- **L04P01** Swimming Pool Facility Management
|
||||
- **L04P02** Book Management System
|
||||
- **L04PE01** Caching and its policies
|
||||
- **L04PE02** Scalable Kitchen Simulation
|
||||
- **L04PE03** Voices in the Void
|
||||
- **L04PE04** The Shaft
|
||||
- **L04PE05** German Meteorological Service
|
||||
- **L03P01** Event Registration Application part 2
|
||||
- **L03P02** Monkey Business
|
||||
- **L03PE01** Online FileFolder
|
||||
- **L03PE02** Shopingu
|
||||
- **L03PE03** Gobblemaps
|
||||
- **L03PE04** Harry Plotter and the Deathly Derivative
|
||||
- **L02P01** Spotify gRPC
|
||||
- **L02P02** TUM Social App
|
||||
- **L02PE01** TUM Social App
|
||||
- **L02PE02** REST Architectural Style Part 2
|
||||
Reference in New Issue
Block a user