[gnutls-help] Asynchronous transport

Yury Shvedov yshvedov at wimarksystems.com
Thu Apr 30 09:49:40 CEST 2015


Thank you for Your reply.

So If i set my pull and push functions, which behave as non-blocking 
sendto and recvfrom respectively, gnutls won't call pull_timeout 
function because of |GNUTLS_NONBLOCK| flag in gnutls_init?

С уважением,
Юрий Шведов
WiMark Systems

On 04/28/2015 02:49 PM, Nikos Mavrogiannopoulos wrote:
> On Tue, Apr 28, 2015 at 11:20 AM, Yury Shvedov
> <yshvedov at wimarksystems.com> wrote:
>> Hi,
>> I have an event-drivent system, based on libevent and extended with my own
>> API and functionality. I'm trying to use gnutls to protect my channels with
>> DTLS, but I'm confused with pull_timeout_function
>> (http://gnutls.org/manual/html_node/Setting-up-the-transport-layer.html). I
>> want to use my own asynchronous timers to tell gnutls about timeouts, but
>> pull_timeout_function make to use select.
>> Is there any way to get round this legally?
> If you are using your own event handling, wouldn't asynchronous
> operation be more suitable? In that case gnutls will not call the
> pull_timeout function.
> http://gnutls.org/manual/html_node/Asynchronous-operation.html#Asynchronous-operation

-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20150430/bb264a63/attachment.html>


More information about the Gnutls-help mailing list