wasync | WebSockets with fallback transports client library

by Atmosphere Java Version: 3.0.2 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | wasync Summary

wasync is a Java library. wasync has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub, Maven.

wAsync is a Java based library allowing asynchronous communication with any WebServer supporting the WebSocket or Http Protocol. wAsync can be used with Node.js, Android, Atmosphere or any WebSocket Framework. To get started, read this super simple Tutorial or read the FAQ. You can browse the javadoc or browse our samples. You can download the jar or use Maven. Life cycle of the underlying Socket can easily be implemented as well. You can also use the specialized clients. For example, to transparently enable Atmosphere's Protocol. or if you want to serialize the fire() method call so events are asynchronously sent in the order the fire method is called. By default, the FunctionResolver will associate the Decoder's type will be used to invoke the appropriate Function, if defined. For example,. will be associated to. You can also implement your own FunctionResolver to associate the Function with Decoder. where myEvent could be read from the response's body. Want to write an Android Client? See.

Support

Quality

Security

License

Reuse

Support

wasync has a low active ecosystem.

It has 163 star(s) with 48 fork(s). There are 24 watchers for this library.

It had no major release in the last 12 months.

There are 21 open issues and 101 have been closed. On average issues are closed in 122 days. There are 2 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of wasync is 3.0.2

Quality

wasync has 0 bugs and 0 code smells.

Security

wasync has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

wasync code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

wasync is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

wasync releases are not available. You will need to build from source code and install.

Deployable package is available in Maven.

Build file is available. You can build the component from source.

Installation instructions are not available. Examples and code snippets are available.

It has 6927 lines of code, 505 functions and 61 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed wasync and discovered the below as its top functions. This is intended to give you an instant insight into wasync implemented functionality, and help decide if they suit your requirements.

Main method for testing
Sets the asynchronous http client
Create a new client instance
Add a header
Completes the socket
Close the socket
Reconnect the request
Create a fire task
Send the given array of Fireloads asynchronously
Handles the handshake
Returns the value joined with the specified delimiter
Closes the socket
Called when the WebSocket connection is open
Handles a status message
Returns a list of parameters
Handles error messages
Invoked when a body is received
Create a new instance of a SerializedRequestBuilder
Compares this object for equality
Create a new request builder
Adds a function to the request
Handles a body request
Returns a string representation of this map
Writes data to the web socket
Called when a body part is received
Decodes a message

Get all kandi verified functions for this library.

wasync Key Features

No Key Features are available at this moment for wasync.

wasync Examples and Code Snippets

No Code Snippets are available at this moment for wasync.

Community Discussions

Trending Discussions on wasync

Embedded Jetty - General SSLEngine Problem - SSLv2Hello disabled error

QUESTION

Embedded Jetty - General SSLEngine Problem - SSLv2Hello disabled error

Asked 2020-Apr-15 at 21:13

When I try to connect to my jetty server, I get the following error(s):

...

ANSWER

Answered 2020-Apr-15 at 21:13

SSLv2Hello is disabled by default on Java 7+

See: https://www.oracle.com/java/technologies/compatibility.html

Your client, the Async Atmosphere client, needs to be either configured or upgraded to use a newer SSL/TLS setup.

Would recommend targeting for a client configuration that is TLSv1.2 or greater. (meaning that SSL, SSLv2, SSLv3, TLSv1.0, and TLSv1.1 are all disabled at the client)

Source https://stackoverflow.com/questions/61205471

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install wasync

You can download it from GitHub, Maven.
You can use wasync like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the wasync component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

wAsync is a Java based library allowing asynchronous communication with any WebServer supporting the WebSocket or Http Protocol. wAsync can be used with Node.js, Android, Atmosphere or any WebSocket Framework. To get started, read this super simple Tutorial or read the FAQ. You can browse the javadoc or browse our samples. You can download the jar or use Maven. Life cycle of the underlying Socket can easily be implemented as well. You can also use the specialized clients. For example, to transparently enable Atmosphere's Protocol. or if you want to serialize the fire() method call so events are asynchronously sent in the order the fire method is called. By default, the FunctionResolver will associate the Decoder's type will be used to invoke the appropriate Function, if defined. For example,. will be associated to. You can also implement your own FunctionResolver to associate the Function with Decoder. where myEvent could be read from the response's body. Want to write an Android Client? See.

Find more information at: