Re: What's bad in Java
- From: "Mike Schilling" <mscottschilling@xxxxxxxxxxx>
- Date: Sun, 1 Jun 2008 21:46:10 -0700
Martin Gregorie wrote:
On Sun, 01 Jun 2008 08:41:19 +0200, Jack wrote:
It's like when you talk with an OSI engineer, and he says to youYou have that backwards. OSI uses a seven layer model. TCP/IP
TCP/IP is slow because there are too much layers.
uses a four layer model which approximates the lowest 5 OSI layers.
TCP/IP provides no equivalent to the Presentation and Application
layers, which are approximated by application-specific protocols,
such as FTP, HTTP or SMTP. These are NOT part of the TCP/IP stack
and
are best thought of as a combination of about half the OSI
Application layer and the application that would sit on top of it.
If you're going to attempt criticism, you should at least get your
facts right before you start.
About 1985 or so, I started (but never had the chance to finish) a
very amusing book written by a TCP expert (perhaps one of its
designers) about OSI, how badly overdosing it was, and how it was
destined to be a colossal failure. The author was entirely correct,
of course, and the amount of money DEC sunk into making Decnet
OSI-compliant was a terrific demonstration of how badly they
misunderstood the market towards the end. If anyone recognizes this
description and can name the book, I'd be grateful.
.
- Follow-Ups:
- Re: What's bad in Java
- From: EJP
- Re: What's bad in Java
- References:
- Re: What's bad in Java
- From: Razii
- Re: What's bad in Java
- From: Jack
- Re: What's bad in Java
- From: Martin Gregorie
- Re: What's bad in Java
- Prev by Date: Resource/File URL Problems, relative links, servlet context and <jsp:useBean..
- Next by Date: Re: What's bad in Java
- Previous by thread: Re: What's bad in Java
- Next by thread: Re: What's bad in Java
- Index(es):
Relevant Pages
|
Loading