Strictly necessary cookies are on by default and cannot be turned off. Functional, Performance and Tracking/targeting/sharing cookies can be turned on below based on your preferences (this banner will remain available for you to accept cookies). You may change your cookie settings by deleting cookies from your browser. Then this banner will appear again. You can learn more details about cookies HERE.
Strictly necessary (always on)
Functional, Performance and Tracking/targeting/sharing (default off)
OK
Help
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

WICED Studio Wi-Fi Combo

Anonymous
Not applicable
‎May 24, 2015 10:38 AM

How come all sockets in wiced_tcp_server_t share a single TLS context object?

In NetX Duo version, at least, wiced_tcp_server_add_tls inits a context object and then adds it to all sockets for this server. But wiced_tls_advanced_context_t object seems to be stateful and connection-specific, and can't be shared from what I can see.

How can concurrent TLS connections work in this implementation? (which is what socket array is for)

Labels
0 Likes
Reply
1 Reply
VikramR_26
Employee
‎Oct 16, 2015 01:38 PM

Re: How come all sockets in wiced_tcp_server_t share a single TLS context object?

We have changed the our Network stack and TLS api's in SDK 3.3.1. Kindly let us know if you still see issues.

0 Likes
Reply