Alternate name for deferred.node()

[kriskowal]

Alex Raschmeyer recommends that we reconsider the name of the node callback function.

http://www.2ality.com/2012/04/expand-urls.html

For what it’s worth, the callback could always be the same object and thus it would make sense for it to be a property rather than a function, but it would incur the cost of generate such a function for every deferred. That is why it is a function. Alternate approaches could simulate a property in some cases.

[domenic]

To get the bikeshedding out of the way: createNodeCallback or asNodeCallback are most to my liking.

I think generating it on each call (and thus being a function instead of a property) makes the most sense, as it seems very rare to want to get the callback more than once.

I suppose for browsers that support getters we could add a nodeCallback lazily-computed property, but I don't know if I liking having a variable API surface depending on environment.

[kriskowal]

Please feel free to shoot down this idea: deferred.nodeback()

[domenic]

I... kind of like it. Why isn't anyone using that term already?

[rauschma]

My proposal: createNodejsCallback. Rationale:

• Makes it obvious that a new object is created for each invocation.

• Callback is more self-explanatory than back.

• The same holds for node versus nodejs. Especially with the DOM, node can mean many things.

• @domenic mentions as as an alternative to create. Another possibility is resolveVia:

  deferred.resolveViaNodejsCallback
  

Having a long identifier here is a feature (not a bug ;-), because that method is so powerful and does so much. Then we want its name to be descriptive.