No, it is not. For the near future, the C ++ Standards Committee has created a research group that is developing a network-level proposal . It looks like they are taking an upward approach, starting at the base level of the socket, and then building support for HTTP / etc. They want to present the main proposal of the socket at the October committee meeting.
As for why they did not put this in C ++ 11, this is purely speculative.
If you want my opinion on this issue, then for this reason.
If you create a program that does something, it has certain functions, you can choose libraries for one of two reasons. One reason is that this library does what it takes to implement your code. And the other - because he does something useful when implementing code in general.
It is very difficult for the design for a particular program to say: "I absolutely must use std::vector to store this list of elements!" The design of the program is not so specific. If you are creating a web browser, the idea of a browser does not bother if it contains its tabs in std::vector , std::list or a user-created object. Now, some designs may strongly suggest certain data structures. But rarely does design explicitly say that something low-level, like std::list , is extremely important.
std::list can be used for almost any program. How can std::vector , std::deque , etc.
However, if you are creating a web browser, bottled as part of this project, it is a network. You must either use the network library or write the network layer yourself. This is a fundamental requirement of this idea.
The term that I use for the former type, for libraries that can be used in all cases, are "useful" libraries.
Threading is a utility library. Design can stimulate flows through the need to respond to the user, but there are ways to respond without proactive multithreading. Therefore, in most cases, threads are the choice of implementation. Threading is a utility.
Not online. You only use the network if your design specifically requires it. You do not decide to simply drop networks into the program. This is not an implementation detail; this is a design requirement.
I believe that the standard C / C ++ library should only implement utilities. This is also why I am against other heavyweight ideas such as XML parsers, etc. This is not because other libraries have these things, but for C and C ++ this is not the best choice.