I watched that long ago and have pretty much forgotten everything I learned. Will try to rewatch at some point. In the other SAs, I took the approach of wrapping the callback within the SA so that calling code didn't have to do it. One could argue that that's the correct approach because, as far as someone calling into a package knows, they are using only Meteor code. Since we, the package authors, chose to use non-meteor code, we should be responsible for doing the wrapping and hiding that complexity from the package user.

But honestly I don't care either way. Currently, only our own fileworker code is calling into the SAs.