Re: [cpp-netlib-devel] FW: body copies on http::client::post

[Nelson, E. - 2 <eri...@ba...>]

> Kim Gräsman wrote on Wednesday October 20, 2010 2:41 PM
 
> Microsoft's STL as of VS2008 doesn't use COW, it uses the small-string
> optimization. Not sure if they went (back?) to COW in 2010, but I
> doubt it.
> 
> LLVM has an interesting sub-project implementing a standard library
> from scratch, and one of the decisions they mention in the overview is
> using small string optimization over COW, as if it was a plain truth;
> http://libcxx.llvm.org/.
> 
> So, I think there's merit to not expecting COW from std::string.
>

STLPort (ships with Sun C++ compilers) doesn't use COW, either.

http://stlport.sourceforge.net/

and the links I put in a previous post

http://bit.ly/hiqqU
http://bit.ly/cqpKVN

have indications in the discussions that gcc may move away from COW
in the future.

Visual Studio 6.0 had well-known thread-safety bugs in its COW
std::string implementation, and was the last version of MSVC to
use COW, according to my understanding.

http://support.microsoft.com/kb/813810
http://www.eggheadcafe.com/software/aspnet/32308437/-thread-safe-stl-for-vc60.aspx


Erik

----------------------------------------------------------------------
This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited. 
Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law. 
The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses. 

References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link: 
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing.