[IGNITE-15795] .NET: Request attributes for a .NET service

• Type: Sub-task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.13
• Component/s: managed services
• Labels: .NET iep-79 ise
• Assignee: Pavel Pereslegin
• Reporter: Pavel Pereslegin
• Created: 20/Oct/21 16:06
• Updated: 29/Mar/22 12:06
• Resolved: 22/Nov/21 07:55

Description

Implement support for passing implicit "request" attributes from the proxy to the .NET service.

Implementation notes.

1. If no caller attributes are passed - there should be no performance overhead when executing service methods.
2. Attributes allow only string and byte[] values and does not permit nulls in key/values.
3. Currently, the context should be immutable, but in the future, it should be possible to change it through the interceptor.
4. Context is bound to the NET proxy invocation handler (not to java invocation handler) and passed as an implicit parameter on every method call.

Public API changes:
API changes are very similar to java part.

New methods in IServices to pass caller context to service proxy.

T GetServiceProxy<T>(string name, bool sticky, IServiceCallContext callCtx) where T : class; 
dynamic GetDynamicServiceProxy(string name, bool sticky, IServiceCallContext callCtx);

New method in IServiceContext for getting caller context inside the service method.

IServiceCallContext CurrentCallContext();

New interface IServiceCallContext.

public interface IServiceCallContext
{
    string Attribute(string name);
    byte[] BinaryAttribute(string name)
}

And the builder ServiceCallContextBuilder to create IServiceCallContext instance.

Issue Links

• relates to: IGNITE-15829 Request attributes for a service in thin clients.
• requires: IGNITE-15794 Request attributes for a java service.
• links to: GitHub Pull Request #9526
• links to: TC2
• links to: TC run all