Re: [cpp-netlib-devel] HTTP Synchronous server reply methods?

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

Dean wrote:
>>> Well, the problem with sending binary data as 7-bit clear over the
>>> network has been documented extensively over the Internet. The spec
>>> clearly states that you have to be transferring data safe to
>>> transfer over 7-bit transfers encoding -- meaning that's technically ASCII
>>> text. It is an accident that images are being sent in the clear as
>>> binary data, and if you notice in history this is largely why people
>>> (browser developers and server developers) had to agree that they
>>> would just take whatever was sent over the wire in the body and just
>>> have the MIME identifiers there.
>>>

Erik wrote:
>> Either way you're sending binary in these examples... the only issue
>> was whether that binary should be copied into a std::string
>
> Why is copying into a string a problem in the first place?
>

It's not... you were talking about the extensively documented problem of sending binary as 7-bit clear on the internet- that seems unrelated to whether or not the netlib container is a std::string or something else.
 

> 
>>> Erik wrote:
>>>> auto_ptr<MyObject> obj(new MyObject);
>>>> response << body(obj);

Dean wrote:
> >> Uh oh, this is dangerous because the user can use the obj right
> after the data is passed to the response.

Erik wrote:
>> Nope- the auto_ptr will be cleared when the ownership transfers to
>> the response, right?


Dean wrote:
> Well, after the `response << body(obj)` line, obj is still accessible
> to the user. It's not guaranteed that the user will do this line at
> the end of the handler body.

Not so.  obj is not accessible if ownership has been transferred to the response.  Two auto_ptrs can't refer to the same object.

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.