Ws.js - A ws-* Implementation of Node.js
DZone's Guide to
Ws.js - A ws-* Implementation of Node.js
Join the DZone community and get the full member experience.
Join For FreeDeploy code to production now. Release to users when ready. Learn how to separate code deployment from user-facing feature releases with LaunchDarkly.
(Get Ws.js on github)
Some time ago I introduced Wcf.js - a wcf-inspired client soap stack for node.js. However Wcf.js itself is a small wrapper on top of Ws.js - the ws-* implementation for node.js. You got it right: Your node.js apps can now access your core services using various ws-* standards. No more proxies for "protocol bridging", no more service rewrites.
Get it here.
Here is a quick sample on what we can do with Ws.js:
The above example adds a username token to the soap. The output soap will be:
For detailed usage instructions check it out on github.
Ws.js currently supports:
Some time ago I introduced Wcf.js - a wcf-inspired client soap stack for node.js. However Wcf.js itself is a small wrapper on top of Ws.js - the ws-* implementation for node.js. You got it right: Your node.js apps can now access your core services using various ws-* standards. No more proxies for "protocol bridging", no more service rewrites.
Get it here.
Here is a quick sample on what we can do with Ws.js:
The above example adds a username token to the soap. The output soap will be:
For detailed usage instructions check it out on github.
Ws.js currently supports:
Deploy code to production now. Release to users when ready. Learn how to separate code deployment from user-facing feature releases with LaunchDarkly.
Like This Article? Read More From DZone
Topics:
Opinions expressed by DZone contributors are their own.
{{ parent.title || parent.header.title}}
{{ parent.tldr }}
{{ parent.linkDescription }}
{{ parent.urlSource.name }}