Additional - too many threads

[Orangeb]

Hello all the patient people for helping me,

I have been looking at the breakdown of data going over a network. The breakdown of it now makes more sense, BUT professor messer talks about trucks moving boxes etc using the roads, and does a metaphor for the breakdown of this. So i now ‘get’ that IP contains TCP and UDP, and that contains HTTP etc. If these are protocols (am I right in saying that)?, then what would you consider ACTUAL data - the characters of a text, or frames of video, if all the packet breakdowns are protocols (which I define as sets of rules). Does that make sense? IP protocols, TCP protocols, UDP protocols, what is the actual info in a message called?

 

[Steveocee]

OSI Model.

/thread

 

[AlphariusOmegan]

ok lets see if i can make this metaphor work for you....
The road is the cabling itself
the truck is the frame, inside the frame you have a box with labels that contain the src/dst MAC addresses and type, inside the box is the data itself. you can't send the data as is, it has to be "packaged" up and labelled correctly just like you would get when ordering from Amazon.
this metaphor is inefficient in that each truck only contains 1 box and if the data cannot be contained within the max size of a frame then it will send a fleet of trucks sufficient to carry all the required boxes that would make up the data with instructions on the label detailing to the destination application how to "unbox" everything in the right order to make sense.