You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If there is more than one language worker to handle an invocation, we need to be able to control where to post an invocation request. This would require setting up inputBuffers on each function load for every language worker that gets initialized.
Need to decouple setting up function invocation inputBuffers from WorkerFunctionDescriptorProvider.cs
The text was updated successfully, but these errors were encountered:
Here is the flow from function load to invocation:
InputBuffer for function invocation on each function is created here:
azure-functions-host/src/WebJobs.Script/Description/Rpc/WorkerFunctionDescriptorProvider.cs
Lines 50 to 59 in 2b8c2b8
On Function Load response from a language worker, inputBuffer is linked to action block which is later used for invocation here:
azure-functions-host/src/WebJobs.Script/Rpc/LanguageWorkerChannel.cs
Lines 366 to 369 in 2b8c2b8
On function invocation, invocationContext is posted here:
azure-functions-host/src/WebJobs.Script/Description/Rpc/WorkerLanguageInvoker.cs
Line 73 in 2b8c2b8
This triggers sending invocation request to language worker here:
azure-functions-host/src/WebJobs.Script/Rpc/LanguageWorkerChannel.cs
Line 373 in 2b8c2b8
If there is more than one language worker to handle an invocation, we need to be able to control where to post an invocation request. This would require setting up inputBuffers on each function load for every language worker that gets initialized.
Need to decouple setting up function invocation inputBuffers from WorkerFunctionDescriptorProvider.cs
The text was updated successfully, but these errors were encountered: