WHY???

when looking at the  OSI model. what happens between a client and a server when requesting a Web page. Oh! and Why should network architects be concerned  with the OSI Model and data frames.......

jayrilla4lifeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

prestonspcworxCommented:
    The OSI Model is just a matter of logically thinking about how a network, works!  It defines how information should be handled when being transported over a network. It defines how software should interact with the network. It sorts network communication functions and divides it into layers.  It specifies how the boundaries between different layers operate. The model specifies the standard interfaces between the layers.  It specifies that any layer's processes should be invisible to the layer above it, and below it.
     Check out the below links, they should enlighten you on how the osi model, and how networks do what they do.  hope this helps!

http://www.webopedia.com/quick_ref/OSI_Layers.asp    --simple descriptions of network layers.
http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito_doc/introint.htm    --much more in-depth descriptions and examples of the network layers.
http://searchnetworking.techtarget.com/sDefinition/0,,sid7_gci523729,00.html    --nice graphic showing layers and items that run at a particular layer.



0
SMartinHamburgCommented:
why not ?
Sorry, a more serious answer:
What is your concern ? As prestonspcworx pointed out in his comment, each layers processes are
invisible to the layers above, so if you are concerned with web design (http, layer 7) you couldn't
care less about bits'n'bytes and routers and cabling length limitation. If you are planing a network
you should know how long each segment can safely get without a repeater (and you can either believe
the manual or go into deth and study how ethernet collision detction works). Unless you are programming
at a lowlevel (talking OSI, not your skills :-)) or are very curious to know what's 'under the hood' you
probably will never have to know anything about data frames.
On the other hand, when I configured the DSL modem and router for my private home network the
delivered manual assumed me knowing all that stuff to understand what they were talking about - so
for once I felt learning this years ago was not in vain :-)
if you have specific concerns or questions on this, don't hesitate ...
Regards


0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Networking Protocols

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.