-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Discussion: Make soap-server operations async #3
Comments
Sure, just fork it. T. From: morganrallen [mailto:[email protected]] Currently calling operations is done synchronously. Not only is this just not the Node way it makes it impossible to use outside async services. — |
@morganrallen Did you make this change already? If not im probably going to do the same thing if it helps |
@MauriceButler |
@morganrallen I actually came to the same conclusion, I did however find this library did async Soap server (as well as client) https://www.npmjs.org/package/soap It dosnt do the automagical wsdl generation but it actually works. |
Currently calling operations is done synchronously. Not only is this just not the Node way it makes it impossible to use outside async services.
I am working with a client who is using node-soap-server as an API endpoint which is require to call an external services for part of its response. I have had to hack in a solution that I do not feel is adequate. I am interested in hearing opinions on improving this moving forward and making it more Node-like.
The text was updated successfully, but these errors were encountered: