Talk:HTTP
Clarify
Again, the task specification is really vague. It only says "Print a URL's content." This rises questions:
- What do you mean by "print"? Print on paper or display on screen? There seems to be both interpretations in current implementations.
- What do you mean by "content"? The source code or rendered page?
Why is it so difficult to write even couple of sentences to specify the task? Specifying the task is the most important part of any software project.
--PauliKL 09:30, 3 October 2008 (UTC)
- Relax, it's fixed. --Mwn3d 12:32, 3 October 2008 (UTC)
- I'm not sure I like the approach. Wouldn't "Display the request content using the most convenient method" be more appropriate? Some languages may not have easy access to the console. --Short Circuit 03:54, 4 October 2008 (UTC)
- That's OK too. --Mwn3d 16:10, 4 October 2008 (UTC)
- I'm not sure I like the approach. Wouldn't "Display the request content using the most convenient method" be more appropriate? Some languages may not have easy access to the console. --Short Circuit 03:54, 4 October 2008 (UTC)
- Fixed? I don't understand this spec. The content of a URL is the interior of the string. What is "source code"? Where in the HTTP specification do they use the term "source code" to denote any portion of the document named by a URI?
- (Please sign your posts). Comments on the change in wording? --Paddy3118 00:54, 20 September 2011 (UTC)
- If you fetch an HTML file, you get HTML source code. This is not true in the general case; http://rosettacode.org/mw/title.png is not the source code of anything. --Kernigh 01:08, 20 September 2011 (UTC)
Not Tested
Well..someone can test C# and Ruby examples? They are working?
ruby is working Rahul 18:47, 5 October 2008 (UTC)
C# (on Mono) is working --ShinTakezou 18:34, 27 January 2009 (UTC)