Description
In many places we require a single-method interface implementation from the user:
TRes Call<TRes>(IComputeFunc<TRes> clo);
All of these can be extended to accept a delegate:
TRes Call<TRes>(Func<TRes> clo);
We can't replace interfaces with delegates completely (which is desirable), because it will take away serialization control from the user. So the interface approach has to stay as a primary.
Delegate support can be added via extension methods, which wrap provided delegates into a class that implements corresponding interface.
Attachments
Issue Links
- is blocked by
-
IGNITE-5329 .NET: Enable peer assembly loading in all APIs
- Open
-
IGNITE-2492 .NET: Peer assembly loading
- Resolved
-
IGNITE-2703 .NET: Dynamically registered classes must use binary serialization if possible
- Resolved
- is related to
-
IGNITE-4339 .NET: Execute .NET code on Java-only nodes
- Open
- links to