On Tue, Nov 22, 2011 at 4:18 PM, wrote:
> In order to detect a "disconnection" by the client i look for a return
> value of 0 from read() in the callback function.
>
> This seems to work correctly when i do a kill -INT on the client or a kill
> -9 on the client: the callback is triggered on the s
On Mon, Oct 3, 2011 at 4:55 PM, Nick Mathewson wrote:
> On Mon, Oct 3, 2011 at 7:35 PM, Dan Kegel wrote:
>> On Mon, Oct 3, 2011 at 4:21 PM, Nick Mathewson wrote:
>>> For more background, folks should see
>>> http://fedoraproject.org/wiki/FedoraCrypt
On Mon, Oct 3, 2011 at 4:21 PM, Nick Mathewson wrote:
> For more background, folks should see
> http://fedoraproject.org/wiki/FedoraCryptoConsolidation and
> http://fedoraproject.org/wiki/CryptoConsolidationEval
http://fedoraproject.org/wiki/Nss_compat_ossl looks sweet.
By the way, OpenSSL does
On Tue, Oct 26, 2010 at 6:48 PM, Nick Mathewson wrote:
> People more experienced than I am about Windows can probably weigh in
> on what the right thing is here.
I think the expectation was that each DLL that uses winsock
would call WSAStartup before using it, and WSACleanup
when done. That's sa
On Wed, Aug 11, 2010 at 12:22 PM, William Ahern
wrote:
>> This code sample does skip the mandatory event_init, but event_del should be
>> more cautious nevertheless.
>
> Why? You'd rather the code do an admittedly needless check millions,
> possibly billions of times per process?
I suppose when c
On Mon, Jul 5, 2010 at 11:17 AM, Phil Budne wrote:
> It's _almost_ enough to make one admit that VMS' "QIO" interface got it right
> (for a narrow class of high-performance server applications).
Yes. I've been regretting how I dismissed it as too complicated
back when I first saw it in its heyda
On Thu, Apr 29, 2010 at 3:41 AM, W.C.A. Wijngaards wrote:
> (From man SSL_write):
> As at any time a re-negotiation is possible, a
> call to SSL_write() can also cause read operations!
>
> It is different from normal socket operations, so maybe an interesting fact.
I haven't looked at li
On Tue, Apr 27, 2010 at 11:47 PM, Denis Bilenko wrote:
> However, some libraries might close the socket while using it in
> another thread.
Heck, they might even do a blocking read, and THEN where would you be?
i.e. if you're using nonblocking I/O, you're kind of an odd duck,
and might have troub
Can you add a build step that verifies the abi has not changed?
On Apr 14, 2010 11:30 AM, "Nick Mathewson" wrote:
On Mon, Mar 29, 2010 at 11:42 AM, Shuo Chen wrote:
> Another patch to make lib...
Hi! I've chatted with Niels, and checked in your patches.
I'm not as familiar with the rpc code a
On Thu, Mar 25, 2010 at 3:00 PM, David Titarenco
wrote:
> Somewhere between 2 and 3 the request is prematurely freed. Any ideas?
Try running your app under valgrind.
***
To unsubscribe, send an e-mail to majord...@freehaven.net w
10 matches
Mail list logo
