Subject: Re: [boost] Asio and SSL problem
From: Carlo Medas (carlomedas_at_[hidden])
Date: 2008-09-05 13:24:24
I was afraid that by uncatching the exceptions in the caller, moreover if in
a multithreaded application, you're going to have for sure an abort, if not
some other side effect in the worst case... (I told you that it was the
stupid one, if you're not a newbie!).
Btw, with boost 1.35.0 and 1.36.0, same stuff but with async methods works
more than perfectly, both if you use client auth or not.
On Fri, Sep 5, 2008 at 5:47 PM, Berserker <berserker_r_at_[hidden]> wrote:
> Thanks for the reply Carlo :)
> > * when you close and connect again, we use 'lowest_layer()' where you
> > 'next_layer()'
> stream::lowest_layer() is only a wrapper around
> "next_layer_.lowest_layer()" where, in case of a "basic_socket" as template
> argument, is:
> lowest_layer_type& basic_socket::lowest_layer()
> return *this;
> So there is no difference with:
> next_layer_type& stream::next_layer()
> return next_layer_;
> > * stupid one (you never know...): are you catching exceptions on the
> > caller? :)
> Sure but I don't think that a stack overflow is a "catchable exception"
> don't you think :) ?
> Cerchi un locale per la serata? Chiedilo a Live Maps!
> Unsubscribe & other changes:
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk