Skip to content

Thread understanding of how frontends are served through the courses #1941

Description

@illicitonion

In ITP we don't really explain that there's a difference between serving over file:// scheme and serving with a static file host like python3 -m http.server. We basically just tell people to do this in the last week of ITP.

Then in SDC we introduce the idea of a backend and that frontends and backends talk to each other.

We've been noticing in mock interviews that almost no trainees have a good mental model for what happens when you open a page in a browser. The idea that first you're making an HTTP GET for a file which is of content-type text/html and then that may trigger other loads, and the JS there may trigger a request of content-type application/json is completely lost on people. They often think all requests to any server must be of content-type application/json.

We probably want to expand the ITP content on "what happens when you load a page" and "why do we need an HTTP server for static frontend files" a little, and then in SDC Decomposition when we introduce backends, add some coverage of what the set of exchanges to load a page actually look like.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions