URGENT | How to implement HTTP in Linux with C and C++, without socket.
ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
@Xeratul - Again, please review the LQ Rules and refrain from posting "cool" code which is unrelated, or unhelpful to the topic of the thread.
Quote:
Do not post if you do not have anything constructive to say in the post.
When posting in an existing thread, ensure that what you're posting is on-topic and relevant to the thread.
It is important to keep the content of threads uncluttered and relevant and easy to understand both for the OP and for all future users who land here seeking solutions to their own problems. If they find pages of pointless code they will simply leave.
Please help us keep the quality of answers on LQ the best on the internet.
@Xeratul - Again, please review the LQ Rules and refrain from posting "cool" code which is unrelated, or unhelpful to the topic of the thread.
It is important to keep the content of threads uncluttered and relevant and easy to understand both for the OP and for all future users who land here seeking solutions to their own problems. If they find pages of pointless code they will simply leave.
Please help us keep the quality of answers on LQ the best on the internet.
I posted this code, because I may think that he needed some simple minimalist examples. When I was learning sockets, I really needed some examples. Without examples of tiny applications, I would have never learned anything.
I may be wrong, but for learning programming, it is important to have, or even to find, small programmes rather than big ones, which are highly complex.
Futhermore, stackoverflow.com is a nice page, but unfortunately, there aren't always complete simple basic codes. This is a reason why I make small programmes for everything. Here, if you look both examples, he may have suffisant information about basics socket, web/http client.
I posted this code, because I may think that he needed some simple minimalist examples. When I was learning sockets, I really needed some examples. Without examples of tiny applications, I would have never learned anything.
...
The OP is not learning sockets - they asked how to do a thing without sockets, and received specific and useful answers.
Please do not continue to drag this thread off that topic, let this end here.
I posted this code, because I may think that he needed some simple minimalist examples. When I was learning sockets, I really needed some examples. Without examples of tiny applications, I would have never learned anything.
I may be wrong, but for learning programming, it is important to have, or even to find, small programmes rather than big ones, which are highly complex.
Futhermore, stackoverflow.com is a nice page, but unfortunately, there aren't always complete simple basic codes. This is a reason why I make small programmes for everything. Here, if you look both examples, he may have suffisant information about basics socket, web/http client.
You are entirely correct about learning programming.
However think back about that learning part.
Did you step up and find examples on your own, or write a one-line request where people then replied giving you tons of examples?
I suspect the first variation. And I feel this is a very important point to teach persons asking LQ questions where they do not yet show the initiative to put in some background effort. Consider a person asking you repeated questions, what you do is eventually enable them to derive these solutions on their own.
Therefore for the OP, or anyone aspiring to write programs of any type, my best recommendation is that they use the references offered earlier in this thread, do further research, start some coding, and follow-up with additional questions. I fully expect that they can find numerous programming examples in many languages, for HTML. I do suspect that they will not find exactly what they are seeking, as we all know that many times we wish to accomplish a certain programming feat, we search the web, do find examples, start with those and then tweak them to suit our current needs.
For all LQ advisors my recommendation is that instead of posting an exact code solutions or a volunteered solution which you personally like, perhaps review the entire thread from the beginning and make a determination whether or not there is anything useful to add, and instead post guidance versus giving someone code. I feel you can argue that the code is already freely available on the web, then my point there is to instead refer to that code using a link, because after all, the original poster of that code was nice enough to post it on the web.
The OP was asked for feedback and clarification, they were given some clear guidance, as well as excellent references.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.