C
CrazedNerd
Guest
So the packet has the header and payload, very simple in terms of a structure, nice.
...But today i've learned that information is surrounded by the frame, which is where the device identification information is located, and would make any human head explode or more likely just cause hyperventilation and panic attacks if they saw it so the folks in software and development soundly leave it out as a courtesy for the end user.
But then what do you call the (FRAME PACKET HEADER PAYLOAD FRAME)? Given how network technology works, if you're not rapidly sending a bunch of what is put in parentheses, your data will get lost and your files will be corrupted. I've seen what happens to a web page when the internet is performing terribly! It is NOT pretty...those bulletin points, hyperlinks that might not even lead anywhere due to data corruption, blank whiteness...NO ADS.
or is it more just like: (FRAME <--- HEADER <---PAYLOAD * thousands, millions, billions)?
...and those encapsulation diagrams are just wrong?
...But today i've learned that information is surrounded by the frame, which is where the device identification information is located, and would make any human head explode or more likely just cause hyperventilation and panic attacks if they saw it so the folks in software and development soundly leave it out as a courtesy for the end user.
But then what do you call the (FRAME PACKET HEADER PAYLOAD FRAME)? Given how network technology works, if you're not rapidly sending a bunch of what is put in parentheses, your data will get lost and your files will be corrupted. I've seen what happens to a web page when the internet is performing terribly! It is NOT pretty...those bulletin points, hyperlinks that might not even lead anywhere due to data corruption, blank whiteness...NO ADS.
or is it more just like: (FRAME <--- HEADER <---PAYLOAD * thousands, millions, billions)?
...and those encapsulation diagrams are just wrong?