JNI: add example threaded client/server applications (JNI only) #212
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds two new JNI-level (not JSSE) examples, a threaded client and server example. The client does session resumption when possible and maintains an application-wide client session cache to hold native
WOLFSSL_SESSION
pointers.examples/SimpleThreadedClient.java
- makes concurrent client connections to a server located atlocalhost:11111
. Default number of client threads is 5, but can be changed using the-n <num_connections>
command line argument. This example implements a simple application-wide Java client cache where nativeWOLFSSL_SESSION
pointers are stored and used for session resumption where possible. See code comments for further explanation.examples/SimpleThreadedServer.java
- starts atlocalhost:11111
and waits for client connections. When a client connection is received, it is handled in a separate thread.ZD 17211