Yamamaya
  Home FAQ Contact Sign in
 
 Advanced search
MATCHING GROUPS



more...
POPULAR GROUPS

more...
found 3 articles for 0.302 sec
Thank you for your advice. Now, it got almost clear! > Writing: > > 1) Acquire the mutex. > > 2) Call SSL_write. If we have sent all of the data, release the lock and > returen. > > 3) If we sent any data, re-adjust to only send the data that remains and go > to step 2. > > 4) If we got a zero, release the lock and return the number of bytes > successfully sent. > > 5) If we got an     

Group: mailing.openssl.users · Group Profile · Search for Yamamaya in mailing.openssl.users
Author: "YAMANEKO/Mao"
Date: Dec 18, 2007 01:01

Yes, the protocol is asynchronous exactly, not "query/response" sequence, and could not re-design it now. I could not find sufficient documents or examples about non-blocking I/O for newbie like me. By way of experiment, I tried to re-write the code again with BIO and non-blocking I/O. The read() wrapping function I made newlly is below; ------- snip ------- BIO_set_nbio( cbio, 1 ) ; BIO_do_connect
Show full article (1.48Kb)
Hello, I'm re-writing an application with OpenSSL. Originally, the application uses only plain TCP socket as a TCP client, it has two threads, receives and submits message asynchronously. Namely, the timing of sending/receiving messages are independent on each other, and there is no logical sequence. How does it possible to do asynchronous read/write with multithread? The outline of the     

Group: mailing.openssl.users · Group Profile · Search for Yamamaya in mailing.openssl.users
Author: "YAMANEKO/Mao"
Date: Dec 17, 2007 21:40

Show full article (1.52Kb)
    

Group: mailing.openssl.users · Group Profile · Search for Yamamaya in mailing.openssl.users
Author: "YAMANEKO/Mao"
Date: Dec 17, 2007 18:11

Show full article (1.86Kb)