Dan Kegel wrote:
Ben Laurie wrote:
Dan Kegel wrote:
I'm adding SSL support to my app, and am finding it
tedious, partly because of having to figure out how
OpenSSL supports nonblocking sockets.
demo/state_machine/state_machine.c is better than nothing,
but it waves its
Dan Kegel wrote:
I'm doing it; right now, I have a single network thread doing all normal
networking *and* SSL; after I write the load tests that demonstrate
how woefully inadequate that is :-), I'll split that into two threads:
one for doing the SSL accept / connect stuff, and one for
Dr S N Henson wrote:
Dan Kegel wrote:
I'm doing it; right now, I have a single network thread doing all normal
networking *and* SSL; after I write the load tests that demonstrate
how woefully inadequate that is :-), I'll split that into two threads:
one for doing the SSL accept / connect
Ben Laurie wrote:
and doesn't actually
use nonblocking sockets.
It doesn't need to! It uses select instead.
To avoid blocking, you *must* use nonblocking I/O even if you use select();
there's no rule saying read() and write() won't block if select()
says they won't;
Yes
Dan Kegel wrote:
Ben Laurie wrote:
and doesn't actually
use nonblocking sockets.
It doesn't need to! It uses select instead.
To avoid blocking, you *must* use nonblocking I/O even if you use select();
there's no rule saying read() and write() won't block if select()
Ben Laurie wrote:
To avoid blocking, you *must* use nonblocking I/O even if you use select();
there's no rule saying read() and write() won't block if select()
says they won't;
Yes there is!
That's debatable. People have been discussing this part of POSIX recently
on
Dan Kegel wrote:
Then you get what is available.
Because you're not using a nonblocking socket, the read()
blocks until the number of requested bytes become available.
You would "get what is available" only if you set the socket into
nonblocking mode.
That is simply not
Dan Kegel wrote:
Ben Laurie wrote:
That is simply not true. The state machine sample would not work AT ALL
if that were the case. But like I say, go ahead, make them non-blocking.
Suits me.
? You're saying that, simply because select() said a file was readable,
that you can read 1024
Dan Kegel wrote:
Dan Kegel wrote:
Then you get what is available.
Because you're not using a nonblocking socket, the read()
blocks until the number of requested bytes become available.
You would "get what is available" only if you set the socket into
nonblocking
Dan Kegel wrote:
Dr S N Henson wrote:
Dan Kegel wrote:
I'm doing it; right now, I have a single network thread doing all normal
networking *and* SSL; after I write the load tests that demonstrate
how woefully inadequate that is :-), I'll split that into two threads:
one for
The following patch adds support for shared libraries on IRIX.
--
albert chin ([EMAIL PROTECTED])
-- snip snip
--- Configure.orig Sat Oct 28 10:20:51 2000
+++ Configure Sun Oct 29 12:35:17 2000
@@ -177,17 +177,17 @@
IRIX 5.x configs
# -mips2 flag is added by ./config when
OpenSSL STATUS Last modified at
__ $Date: 2000/10/26 21:07:27 $
DEVELOPMENT STATE
o OpenSSL 0.9.7: Under development...
o OpenSSL 0.9.6: Released on September 24th, 2000
o OpenSSL 0.9.5a: Released on April
Dr S N Henson wrote:
I'm doing it; right now, I have a single network thread doing all normal
networking *and* SSL; after I write the load tests that demonstrate
how woefully inadequate that is :-), I'll split that into two threads:
one for doing the SSL accept / connect stuff,
%% Rich Salz [EMAIL PROTECTED] writes:
rs My questions about locality, however, are still highly pertinent.
rs Let's look at IDEA, and let's assume that the OpenSSL README is
rs correct in stating that IDEA is not patentented in Australia, but
rs is patented in the UK. If OpenSSL were
14 matches
Mail list logo
