@robfallows haha this is insane, I was just composing my answer when you mentioned me
@skydog I’m using zardak:soap as a consumer in a project right now and it is working well.
It is actually a thin wrapper around https://www.npmjs.com/package/soap which is an npm package for the node ecosystem. It is not intended specifically for Meteor, in fact it has nothing to do with Meteor except that zardak was kind enough to create the wrapper and publish it on atmosphere.
This package, with or without meteor, can also be used as a service endpoint.
Meteor is all about isomorphic, reactive applications which focus heavily on real time aspecs of an application.
Soap on the other hand is a technology from a different era and is designed to be a request/response method of interfacing with an application.
If you are developing your soap service to interface with an existing application or database, I think you should be doing that with plain node, using the soap package from npm. This is assuming the existing applicaton does not provide its own integration libraries you can consume on a different platform, which would be far easier to do.
So, if you want to discuss this further, I’d ask you to share a bit more about what you want to achieve so that we could talk specifics.