<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title><![CDATA[wolfSSL - Embedded SSL Library — C# Wrapper - Set non-blocking I/O]]></title>
		<link>https://www.wolfssl.com/forums/topic1040-c-wrapper-set-nonblocking-io.html</link>
		<atom:link href="https://www.wolfssl.com/forums/feed-rss-topic1040.xml" rel="self" type="application/rss+xml" />
		<description><![CDATA[The most recent posts in C# Wrapper - Set non-blocking I/O.]]></description>
		<lastBuildDate>Tue, 11 Jul 2017 23:25:05 +0000</lastBuildDate>
		<generator>PunBB</generator>
		<item>
			<title><![CDATA[Re: C# Wrapper - Set non-blocking I/O]]></title>
			<link>https://www.wolfssl.com/forums/post3366.html#p3366</link>
			<description><![CDATA[<p>Hi Jacob,</p><p>Thanks for your answer, the game is in a really early state, I am just setting the barebones of the server/client network exchange, so there is no hurry yet.</p><p>Actually, I have managed to get the client working on multithreading (the client was the problem) so maybe I would be able to sort out the problem, having the blocking functions (wolfssl.accept(), etc.) being called in a separate thread, so maybe I won&#039;t need the non-blocking setup, but it&#039;s not definitive as I haven&#039;t tested yet a real connection between server and client.</p><p>Anyway it would be nice to have this funcionality wrapped in future releases, by now I will be dealing with C# threading and wolfssl. Would you think I should expect major problems with these two working together?</p><p>Thanks a lot! I&#039;ll reply with news.</p>]]></description>
			<author><![CDATA[null@example.com (Ivanchez)]]></author>
			<pubDate>Tue, 11 Jul 2017 23:25:05 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post3366.html#p3366</guid>
		</item>
		<item>
			<title><![CDATA[Re: C# Wrapper - Set non-blocking I/O]]></title>
			<link>https://www.wolfssl.com/forums/post3365.html#p3365</link>
			<description><![CDATA[<p>Hi Ivanchez,</p><p>There is not yet a wrapping of the function wolfSSL_set_using_nonblock in the C# wrapper. It would be similar to how the function wolfSSL_get_error is wrapped in wolfSSL.cs but would the function would need to be added in. With the C# wrapper the examples are currently set up to use blocking sockets (<a href="https://github.com/wolfSSL/wolfssl/blob/master/wrapper/CSharp/wolfSSL_CSharp/wolfSSL.cs#L454">https://github.com/wolfSSL/wolfssl/blob … SL.cs#L454</a>) so the IO callbacks would also need to be set up for the project. An example of setting the IO callback can be found here <a href="https://github.com/wolfSSL/wolfssl/tree/master/wrapper/CSharp/wolfSSL-Example-IOCallbacks.">https://github.com/wolfSSL/wolfssl/tree … Callbacks.</a></p><p>What are the time frames with building the game for when it would be needed?</p><p>Regards,<br />Jacob</p>]]></description>
			<author><![CDATA[null@example.com (Jacob)]]></author>
			<pubDate>Tue, 11 Jul 2017 22:59:35 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post3365.html#p3365</guid>
		</item>
		<item>
			<title><![CDATA[C# Wrapper - Set non-blocking I/O]]></title>
			<link>https://www.wolfssl.com/forums/post3363.html#p3363</link>
			<description><![CDATA[<p>Greetings,</p><p>I&#039;m trying to use the c# wrapper to build a little client for a game using DTLS. The only problems is that I need to have a non-blocking setup, since it&#039;s mandatory for the application. I know there is the <strong>wolfSSL_set_using_nonblock</strong> function in the native library, but I can&#039;t find any similiar one inside the c# wrapper.</p><p>Then, the question is: <br />Is there any way to set non-blocking I/O in c#?</p><p>Thanks!</p>]]></description>
			<author><![CDATA[null@example.com (Ivanchez)]]></author>
			<pubDate>Mon, 10 Jul 2017 15:14:35 +0000</pubDate>
			<guid>https://www.wolfssl.com/forums/post3363.html#p3363</guid>
		</item>
	</channel>
</rss>
