Pulling this line of discussion into an issue rather than in-line comments in a merged PR.

"Archived" comments below came from this PR

WesTyler 13 minutes ago • edited Member

@dhinklexo does calling something like response.send(payload) from within the method (like toki-method-http) simply attach that payload to the response that will eventually be sent by Toki? Or does it actually fire off the response object back to the client?

Basically do the toki plugins act like hapi prerequest handlers/decorators, or like the actual request handlers?

WesTyler 12 minutes ago Member

Or is this just a response object that is sent back to Toki to map to the main response and runtime context?

dhinklexo 9 minutes ago Member

(Context)
This is just a copy of the bridge response/request API

(Answer)
It looks like that IS the current behavior. Whether or not that's the desired behavior on the other hand..

WesTyler 4 minutes ago Member

My understanding from our initial talks about toki-method-http and toki-method-rabbit is that the method should define the shape of its result (via templated config) and do 2 things:

1. pass that response back to toki, which will add it to the runtime context under the action's name property. future potential actions now have access to this mapped result.
2. modify the "main" response object without sending it back to the client. This way toki can build up the main response by running it through all of the methods, then at the end send the total hydrated response back to the requesting client.