asyncp | Port of the async library to use Promises | Reactive Programming library

by jgornick JavaScript Version: Current License: MIT

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

kandi X-RAY | asyncp Summary

asyncp is a JavaScript library typically used in Travel, Transportation, Logistics, Programming Style, Reactive Programming, Nodejs applications. asyncp has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can install using 'npm i asyncp' or download it from GitHub, npm.

asyncp is a port of the async library to use Promises instead of Node.js callbacks.

Support

Quality

Security

License

Reuse

Support

asyncp has a low active ecosystem.

It has 27 star(s) with 2 fork(s). There are 3 watchers for this library.

It had no major release in the last 6 months.

There are 2 open issues and 1 have been closed. On average issues are closed in 31 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of asyncp is current.

Quality

asyncp has 0 bugs and 0 code smells.

Security

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

asyncp code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

asyncp is licensed under the MIT License. This license is Permissive.

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

Reuse

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

Deployable package is available in npm.

Installation instructions, examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of asyncp

Get all kandi verified functions for this library.

asyncp Key Features

No Key Features are available at this moment for asyncp.

asyncp Examples and Code Snippets

No Code Snippets are available at this moment for asyncp.

Community Discussions

Trending Discussions on asyncp

How to get Fiddler or Charles to capture traffic from Unity 2018 IL2CPP apps

QUESTION

How to get Fiddler or Charles to capture traffic from Unity 2018 IL2CPP apps

Asked 2020-Feb-27 at 21:04

I have built apps with Unity 5 and with Unity 2017, and am able to use Fiddler or Charles to capture network traffic successfully. However, When I build a Unity 2018 app using IL2CPP (the other apps were built with .Net), the app works (successfully sending network traffic), but the app seems to somehow bypass the Fiddler (or Charles) proxy. That is, Fiddler and Charles are unable to show the network traffic from the Unity 2018 IL2CPP app, even though it can show traffic from Unity 5 and Unity 2017 apps.

Note that everything works with Unity 5 and Unity 2017, and, that the SSL settings, etc. have been setup previously. Also, I have used the Fiddler "WinConfig" to EnableLoopback for the Unity 2018 app.

My question is: What do I need to do to get a Unity 2018 IL2CPP app to show traffic in Fiddler or Charles?

Update: Here is some sample code that shows that HttpClient requests don't go through the proxy, but other (Unity) webrequests do go through the proxy:

...

ANSWER

Answered 2020-Feb-27 at 21:04

Unity has acknowledged that this is a problem:

https://fogbugz.unity3d.com/default.asp?1222589_u6qsndet3umnp50u

https://issuetracker.unity3d.com/issues/httpclient-ignores-windows-proxy

It appears that during the "IL2CPP" code generation process, the generated code changes the HttpClient to not use the local proxy.

The code below was copied from here, and seems to overcome the Unity IL2CPP bug:

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

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

Vulnerabilities

No vulnerabilities reported

Install asyncp

You could also download an archive (zip or tar.gz) from the asyncp Github Releases.

Support

API documentation is coming soon, but... Because this is a port of the async library, the API should be the same. Existing async documentation can be found here. The biggest difference is that there won't be a final callback argument. Instead of the callback, the resolved Promise is equivalent. Another difference is when an async iteratee, task, callback, etc... could allow multiple result arguments, they will be represented as an array of results in the resolved Promise. This concept is similar to Bluebird.spread.

Find more information at: