Dept-of-names-dpt: callback/callable API fn

[zippy]

Currently we have named developer callable functions (like commit()) "API functions" and we have named holochain callable functions (like genesis()) "callback functions" following what we did in the go version.

In reality both of these are API functions, and "callback" isn't the correct word because it suggests to the developer that the calling from the system follows from some initial call made by the developer, which is not the case.

We need terms to distinguish these two types of API functions based on "who" calls them, the developer, or the Holochain system.

[Connoropolous]

For "callbacks"... related words to use might be like... "invoked" and "hooks"

[ddd-mtl]

I would suggest renaming "callbacks" to "hooks"
I think that's how they call them in Drupal.
"API" seems fine to me. As an app developer that's how I would think of the functions that I can invoke.

[Connoropolous]

+1 for "hooks"

One weird one is "receive" ... I don't know where that belongs, or under what name. You mentioned "communication" in a review Damien. Maybe it's its own category

[zippy]

The problem with "hook" is that it always is about additional access to an existing flow, like how the programmer gets to insert control. That's not what's going on here in most cases, these are often required functions to implement. There's really no such thing as a "required hook" which is what most of them are.

How about "API callable functions" and "API expected functions"?

[ddd-mtl]

I suggested 'Communication' for the name of the capability where receive would live, because the refactor doc mentioned "web_gateway" but its more than just "web"...

I agree with Eric about 'hooks', but I'm not comfortable with the 'callable/expected' proposal.
Lets take more time to think about this.