OSI - 401-advanced-javascript-aimurphy/seattle-javascript-401n13 GitHub Wiki
Open systems
A Priest saw ten nuns do pushups!
Application: user end layer client Presentation: server to client Session: server Transport: fire event form my machine and send it over the network for other ppl Network Datalink Physical
TCP moves things in big quantity--but gets straight to work, but doesn't know how much stuff.
- http works on tcp and you need everything before you can go--and ACTUAL bit at a time. All or nothing vs you know when and what is coming down the schute.
UDP carries more info in the initial stages and gives you info
- more like netflix you can have a bit at a time, like buffering
example (pubsub--observer pattern):
APP @1039 has a db that can save and delete and emit data
SERVER hears the event emitted--('i got data over TCP') will read the data in and figure out what to do. ^to do this it will need the event name and some payload(some sort of datat) then it will send it out to clients. it is the middleman between the app and clients
CLIENT connect to the server and wait.... once they hear the event and process it.
sources:
also refer to FRV day: 8/10 for timestamps