Skip to content

Latest commit

 

History

History
81 lines (62 loc) · 2.31 KB

README.md

File metadata and controls

81 lines (62 loc) · 2.31 KB
Raw

diagrams

part0b, 1st diagram

sequenceDiagram
    participant browser
    participant server
    browser->>server: GET https://studies.cs.helsinki.fi/exampleapp/
    activate server
    server-->>browser: HTML document
    deactivate server
    browser->>server: GET https://studies.cs.helsinki.fi/exampleapp/kuva.png
    activate server
    server-->>browser: the png pic
    deactivate server
    Note right of browser: Page with a pic will is rendered
Loading

part0b, 2nd diagram

sequenceDiagram
    participant browser
    participant server
    
    browser->>server: GET https://studies.cs.helsinki.fi/exampleapp/notes
    activate server
    server-->>browser: HTML document
    deactivate server
    
    browser->>server: GET https://studies.cs.helsinki.fi/exampleapp/main.css
    activate server
    server-->>browser: the css file
    deactivate server
    
    browser->>server: GET https://studies.cs.helsinki.fi/exampleapp/main.js
    activate server
    server-->>browser: the JavaScript file
    deactivate server
    
    Note right of browser: The browser starts executing the JavaScript code that fetches the JSON from the server
    
    browser->>server: GET https://studies.cs.helsinki.fi/exampleapp/data.json
    activate server
    server-->>browser: [{ "content": "HTML is easy", "date": "2023-1-1" }, ... ]
    deactivate server    

    Note right of browser: The browser executes the callback function that renders the notes
Loading

part4d, diagram

sequenceDiagram
    participant user
    participant browser
    participant backend
    
    Note left of user: User fills in login form with username and password
    user->>browser: login button pressed
    
    activate backend
    browser->>backend: HTTP POST /api/login { username, password }
    
    Note left of backend: backend generates a TOKEN that identifies the user
    backend-->>browser: TOKEN returned as message body
    deactivate backend
    
    Note left of browser: browser saves the TOKEN
    
    Note left of user: User creates a note 
    user ->> browser: create note button pressed
    
    activate backend
    browser ->> backend: HTTP POST /api/notes { content } TOKEN in header
    Note left of backend: backend identifies the user from the TOKEN

    backend -->> browser: 201 created
    deactivate backend
Loading