I'm a teapot
-
Pfffft! Call me when it finally implements RFC1149 - or preferably RFC2549. :-D
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
That's Level 1 of the OSI levels. HTTP is what, level 4?
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
-
That's Level 1 of the OSI levels. HTTP is what, level 4?
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows. -- 6079 Smith W.
Certainly more like Presentation (6) or Application (7). The encoding - the specific use of angle brackets, character entities and that sort of stuff - is a Presentation issue. That is how to represent an abstract information structure that might equally be represented in other ways (such as a DOM tree). The syntax and semantics of that abstract part of HTML belongs in Application. Even though many people (usually with rather shallow knowledge of the OSI model - but that covers 95+ % of all software developers today) try to place various elements of IP based protocols into one single OSI layer, it usually can't be done properly, as seen from an ISO model point of view. In plain words: IP protocols are a mess in regard to clean layering.
-
Pfffft! Call me when it finally implements RFC1149 - or preferably RFC2549. :-D
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
Certainly more like Presentation (6) or Application (7). The encoding - the specific use of angle brackets, character entities and that sort of stuff - is a Presentation issue. That is how to represent an abstract information structure that might equally be represented in other ways (such as a DOM tree). The syntax and semantics of that abstract part of HTML belongs in Application. Even though many people (usually with rather shallow knowledge of the OSI model - but that covers 95+ % of all software developers today) try to place various elements of IP based protocols into one single OSI layer, it usually can't be done properly, as seen from an ISO model point of view. In plain words: IP protocols are a mess in regard to clean layering.
Which do you mean, OSI or ISO?
The difficult we do right away... ...the impossible takes slightly longer.
-
Which do you mean, OSI or ISO?
The difficult we do right away... ...the impossible takes slightly longer.
I'm fairly sure he means the OSI model[^].
Robust Services Core | Software Techniques for Lemmings | Articles
The fox knows many things, but the hedgehog knows one big thing. -
Which do you mean, OSI or ISO?
The difficult we do right away... ...the impossible takes slightly longer.
-
Pfffft! Call me when it finally implements RFC1149 - or preferably RFC2549. :-D
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
-
I'm happy to announce that the http module in Python 3.9 [now includes](https://bugs.python.org/issue39507) the HTTP 418 "I'm a Teapot" code. For those wondering what I'm talking about, see [RFC 7168: The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)](https://www.rfc-editor.org/rfc/rfc7168#section-2.3.3)
Quote:
2.3.3. 418 I'm a Teapot TEA-capable pots that are not provisioned to brew coffee may return either a status code of 503, indicating temporary unavailability of coffee, or a code of 418 as defined in the base HTCPCP specification to denote a more permanent indication that the pot is a teapot.
Yeah, it's going to be one of those weeks.
cheers Chris Maunder
I got all excited. I thought you were talking about a container for the Tiny Encryption Algorithm (TEA)[^], which I've used a number of times.
Software Zen:
delete this; -
Certainly more like Presentation (6) or Application (7). The encoding - the specific use of angle brackets, character entities and that sort of stuff - is a Presentation issue. That is how to represent an abstract information structure that might equally be represented in other ways (such as a DOM tree). The syntax and semantics of that abstract part of HTML belongs in Application. Even though many people (usually with rather shallow knowledge of the OSI model - but that covers 95+ % of all software developers today) try to place various elements of IP based protocols into one single OSI layer, it usually can't be done properly, as seen from an ISO model point of view. In plain words: IP protocols are a mess in regard to clean layering.
Having been out of the developer world through the era when HTCPC was created, I am made very curious: was this created to illustrate the OSI model? Thanks for the lessons; I've always believed that shared development relied entirely on communication of purpose and methods. There is nothing so satisfyingly helpful as a well-made requirements doc.
-
Having been out of the developer world through the era when HTCPC was created, I am made very curious: was this created to illustrate the OSI model? Thanks for the lessons; I've always believed that shared development relied entirely on communication of purpose and methods. There is nothing so satisfyingly helpful as a well-made requirements doc.
-
I'm happy to announce that the http module in Python 3.9 [now includes](https://bugs.python.org/issue39507) the HTTP 418 "I'm a Teapot" code. For those wondering what I'm talking about, see [RFC 7168: The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)](https://www.rfc-editor.org/rfc/rfc7168#section-2.3.3)
Quote:
2.3.3. 418 I'm a Teapot TEA-capable pots that are not provisioned to brew coffee may return either a status code of 503, indicating temporary unavailability of coffee, or a code of 418 as defined in the base HTCPCP specification to denote a more permanent indication that the pot is a teapot.
Yeah, it's going to be one of those weeks.
cheers Chris Maunder
Reminds me of one of the clauses from [RFC1122 (Requirements for Internet Hosts - Communication Layers)](https://datatracker.ietf.org/doc/html/rfc1122) - that said software should be "Able to leap tall buildings at a single bound". We found that when it was copied verbatim into an early draft of requirements for avionics compatible Ethernet (including UDP, TCP and IP layers)... Needless to say, it was swiftly removed! PS - I hope you're [*this* teapot](https://en.wikipedia.org/wiki/Utah\_teapot)...
Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
-
I'm afraid that you can forget any hope of learning anything from OSI. It was thrown away, all its qualities were ditched. OSI is just for old time dreamers fantasising about how the world could have been. If the world wasn't different, of course ...
-
I'm happy to announce that the http module in Python 3.9 [now includes](https://bugs.python.org/issue39507) the HTTP 418 "I'm a Teapot" code. For those wondering what I'm talking about, see [RFC 7168: The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)](https://www.rfc-editor.org/rfc/rfc7168#section-2.3.3)
Quote:
2.3.3. 418 I'm a Teapot TEA-capable pots that are not provisioned to brew coffee may return either a status code of 503, indicating temporary unavailability of coffee, or a code of 418 as defined in the base HTCPCP specification to denote a more permanent indication that the pot is a teapot.
Yeah, it's going to be one of those weeks.
cheers Chris Maunder
I don't care... I get my coffee every morning at a local eatery... :)
Steve Naidamast Sr. Software Engineer Black Falcon Software, Inc. blackfalconsoftware@outlook.com
-
I'm happy to announce that the http module in Python 3.9 [now includes](https://bugs.python.org/issue39507) the HTTP 418 "I'm a Teapot" code. For those wondering what I'm talking about, see [RFC 7168: The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)](https://www.rfc-editor.org/rfc/rfc7168#section-2.3.3)
Quote:
2.3.3. 418 I'm a Teapot TEA-capable pots that are not provisioned to brew coffee may return either a status code of 503, indicating temporary unavailability of coffee, or a code of 418 as defined in the base HTCPCP specification to denote a more permanent indication that the pot is a teapot.
Yeah, it's going to be one of those weeks.
cheers Chris Maunder
-
This message was caught by the spam filter and I won't lie when I say I took my time hitting the "let this one through" button ;)
cheers Chris Maunder
-
Pfffft! Call me when it finally implements RFC1149 - or preferably RFC2549. :-D
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
