I see many replies with the Please Do Not Throw Sausage Pizza Away, but I was taught with Please Do Not Throw Soggy Pizza Away. Is this a geographical thing or was my instructor just weird and liked 'soggy' pizza. I once had a cheese pizza with like a layer of oil on it. I would call that soggy.
A brilliant friend of mine, alas now gone from this world, used to explain the OSI model by using the Mafia hierarchy as an analogy. Given many governments in this world are increasingly looking like criminal Mafia organizations, this might be even more germane.
The further you sit from the kitchen the longer you wait for burger.
The kitchen checks your order against the ticket.
The tables have numbers to coordinate orders.
A runner brings your burger.
The POS tracks your orders & payment.
The menu shows you available burgers.
The cafe sells you burgers.
It's easier than that. "Remember when you gave your kid who wants to help but is kinda useless some fake work to do so they'd stay out of your way? In this case, the fake work was the whole OSI project."
When working in IT customer support, I sometimes did the "sorry sir, your error clearly sits in OSI layer 8" to blow off some steam, and I always got away with it.
Funny that I've spent most of my career working on layers 1 and 7 and never all the stuff that makes either of those matter. God save the digital glue that holds us all together
Even if it were, you’d have to covert back to football field lengths.
I’m still trying to understand how Americans eat their burgers from the bottom up.
Well not really. That would imply that each layer in the OSI stack did the same thing. More like a big Mac with all the fixings maybe? 2 all beef patties, special sauce, lettuce, cheese, pickles, and a sesame seed bun.
Years ago I was talking to the guy who was in charge of education at Novell and he told me that when he took his networking technologies exam the testing center had a framed poster of the OSI model inside the testing room. Every exam question he had was answered by the poster!
I would say 7 ingredients. Just to give them the idea of different functions. I'm american BTW, love burgers, and took a couple of classes that discussed the OSI model. Will always prefer burgers...
Not quite. It’s more like seven floors in a building connected by a mail tube. Each floor does something different and can talk only to the floor above or below.
Hey now....some of us in the USA learned it as a boring rote memorization PowerPoint slide in the Army....because the instructor was from a southern state and had never seen a computer before joining
I bet @tracketpacer.bsky.social would accept the challenge. I'm just trying to figure out why 7 patties, since that assumes all layers are equal and consistent. Maybe 7 components making the burger complete and in your hand is better? It is 3 AM and the smoke detector battery chirp woke me...
True on the ubiquity of the burger; but also any adult American that’s not a bit familiar with a seven-layer dip has been leading a sheltered and deprived food life.
Good point on middle and high school students. The OSI model wasn’t well known when I was in Jr and Sr high, and was invented at the end of my grade school years.
wait wait slow down. so a burger needs to explain a burger to me... and you say the first burger needs to imagine if another burger had 7 more patties? can you make this a marvel movie by chance?
Physical Layer - the burger
Data Link Layer - the smell
Network Layer - your eyes
Transport Layer - your hands
Session Layer - you pick it up
Presentation Layer - you taste it
Application Layer - the taste matches the smell and eyes
Are they different flavored patties?
One's with cheese or peppers or bacon?
Are they different flavored garden burgers?
What ever happened to the Pizza flavored garden burgers?
Why would you need an explanation, when the model is as logical as can be?
More logical to explain, as explaining why you would need a burger with 7 patties 🤔
What does being American have to do with not understanding the OSI model?
Check the syntax in the presentation layer cause your application is throwing errors.
Really wanna fuck with then, replace some of those patties with veggie toppings…..application layer is a tomato, presentation layer is an onion, session layer lettuce
No, it's just hardware, tools and applications became so good it's rare you actually need to know the Legos unless you're building software, hardware and networks at a low level.
Is all abstracted away from you, even logs and config in most cases.
I was there in the original battle in America, when the layer model was being explained and meanwhile the TCP/IP stack was implemented while the committees were discussing it.
Some would give up at the salad layer. And might be disappointed that the application layer doesn't involve mega-killer spicy bbq sauce.
Also, since they tend to measure things differently, bandwidth would be donuts per barrel gauge, and latency would be measured in spoons times eagle feathers.
Honestly, I found all the analogies more confusing than just thinking about how data has to flow from the application down the os to the network and back.
App does stuff, transforms that stuff into other stuff that the os understands, os transforms that stuff into stuff the network understands.
And this is all to build and maintain a post office for stuff. All the things doing the stuff transformations have different handshakes, languages, and secret phrases.
The wires and signals between computers on a network become more and more abstract as you go…yeah, hearing myself I think you have the correct attitude.
Comments
Princess Diana Never Tried Sex (with) Prince Andrew…
Physical, Datalink, Network, Transport, Session, Presentation, Application
Also:
Layer 8: Financial
Layer 9: Political
https://bsky.app/profile/dontbecon-d.bsky.social/post/3lctkj375p22g
User
Needs
Training
Problem Exists Between Keyboard And Chair
Please Do Not Throw Sausage Pizza Away.
I’m from NYC!
was how I learned it too
Are layer 8 and 9 condiments?
Very easy to remember!
j/k - It's from In-N-Out Burger in CA. You can order stuff like this off-menu. Mostly for college pranks.
Layer 0: laws of physics. (My addition.)
Layer 1: hardware. Wires, radio waves, carrier pigeons etc.
Layer 2: point-to-point comms.
Layer 3: routing.
Layer 4: end-to-end (nodes).
Layer 5: endpoint-to-endpoint (processes).
Then: Where does IEEE 802 fit in?
The kitchen checks your order against the ticket.
The tables have numbers to coordinate orders.
A runner brings your burger.
The POS tracks your orders & payment.
The menu shows you available burgers.
The cafe sells you burgers.
And they each have their own security wrapper.
I could go OMAD (One meal A Day) on that.
Pull
Down
kNickers
To
See
Pubic
hAir
(I won’t repeat the acronym we used to use to remember resistor values 🙄)
https://www.allrecipes.com/recipe/23176/seven-layer-dip-ii/
(In the U.S. it's a 4.375 layer model... you gotta divide by 1.6.)
I’m still trying to understand how Americans eat their burgers from the bottom up.
I'm just not being brow beaten by acronyms.
This is coming from someone that first was thinking OSI Rio and corrected myself to OSS Rio - funny movie.
https://www.6connect.com/blog/moment-internet-history-osi-7-layer-burrito/amp/
(Scribbling on Post-it) ... "Note to self: study the OSI model". (Sticks Post-it to monitor to be ignored.)
I think I’m in the wrong line again.
Could be an interesting children’s game.
https://www.delish.com/cooking/recipe-ideas/a25741035/7-layer-dip-recipe/
And then there's just people like me who hate seven layer dip. That shit's disgusting.
Data Link Layer - the smell
Network Layer - your eyes
Transport Layer - your hands
Session Layer - you pick it up
Presentation Layer - you taste it
Application Layer - the taste matches the smell and eyes
One's with cheese or peppers or bacon?
Are they different flavored garden burgers?
What ever happened to the Pizza flavored garden burgers?
Yes, I know, I'm short one....
More logical to explain, as explaining why you would need a burger with 7 patties 🤔
Wouldn’t be able to get fries the burger would have an entire days calorie requirement 💀
I want a Pounder damn it.
Check the syntax in the presentation layer cause your application is throwing errors.
Good times
*slams table*
TCP/IP Model ? 😏
Is all abstracted away from you, even logs and config in most cases.
So dont try
Also, since they tend to measure things differently, bandwidth would be donuts per barrel gauge, and latency would be measured in spoons times eagle feathers.
App does stuff, transforms that stuff into other stuff that the os understands, os transforms that stuff into stuff the network understands.