lihaoyi
commented
7 years ago Something like
- AutowireServer.route[Api](service)(autowire.Core.Request(url, body))
+ AutowireServer.route[Api](new MyService(extraArg))(autowire.Core.Request(url, body))Where
trait Api{
def methodA(a: Int): String
}
class MyService(extraArg: Thingy) extends Api{
def methodA(a: Int): String = {
doSomething(a, extraArg)
}
}This is the general technique you can use for injecting "side-channel" information into your autowire methods: request metadata, user session, authentication credentials/tokens, logging context, etc. etc.
At some point this should make it into the docs; if someone wants commit access to help freshen them up I'd gladly give it
bbarker
ryejoon
Sorry if this has been addressed before (tried a few searches without luck):
I haven't been able to think of a good way to inject additional information into an autowired API call on the server side. Traditionally, we might use an additional parameter to our API function ... but the fact that, on the server side, the API service is being abstractly handled as follows:
combined with the fact that the additional parameter wouldn't exist on the client, seems to make this impossible or non-obvious.
Example use case: running an API command that has metadata as a parameter - the server needs to fill in the remote ip address as a field in the metadata, since the client can't be trusted to do this.