[DISCUSS] Custom service proxy context

2021-10-08 Thread Pavel Pereslegin
Hello Igniters! I want to implement a feature to support a custom "caller" context in ignite services (see example in ticket description [1]). Sometimes, when using Ignite services, it becomes necessary to pass custom parameters from the "request source" to the service. This is most commonly used

Re: [DISCUSS] Custom service proxy context

2021-10-08 Thread Eduard Rakhmankulov
Hi, Pavel Is it possible to provide type-safe API for ServiceProxyContext ? I think constructions like int arg1 = ctx.attribute("arg1"); are error prone. Can we make something like this : //Signature with two generic params which allow the compiler to check if the service will be called with the

Re: [DISCUSS] Custom service proxy context

2021-10-08 Thread Pavel Pereslegin
Hi, Eduard! Thanks for your feedback. The idea sounds very good, but don't forget about the platform services. For example, we may call Java service from .Net and vice-versa. I'm not sure if the context can be implemented as a custom class (instead of Map/Dictionary) in this case. пт, 8 окт. 202

Re: [DISCUSS] Custom service proxy context

2021-10-08 Thread Eduard Rakhmankulov
I am not aware .NET capabilities, but as I can see service must be implemented in *java* and even if can't serialize other that Map on .NET side, on java side we can wrap this map with provided TypedContext (context should be convertible from map in this case). That leads to a situation when Java c

Re: [DISCUSS] Custom service proxy context

2021-10-08 Thread Igor Sapego
Hi guys, Why can not a user implement such context on application level? I believe Ignite provides all necessary tools for that. User can just implement such a context as user type and pass it to services they need. Are the arguments why would Ignite need a separate feature for such a use case? B

Re: [DISCUSS] Custom service proxy context

2021-10-08 Thread Pavel Tupitsyn
Agree with Igor. I'm not sure this feature is a good fit for Ignite. Ignite should not be responsible for such a high-level concept, this should be on the application side instead. - As Eduard noted, it is hard to make this type-safe - Ambient state is not obvious and the API looks confusing even

Re: [DISCUSS] Custom service proxy context

2021-10-08 Thread Pavel Pereslegin
Igor, Pavel. > Why can not a user implement such context on application level? I believe > Ignite provides all necessary tools for that. The user wants to trace the source of the service call. For example, a service must log the name of the user who made the calls of the service. For now, there's

A new feedback has been added : 19

2021-10-08 Thread Bugyard
A new feedback has been added, go to bugyard.io to see all the details... https://bugyard.io A new feedback has been added "We don't have code samples for .NET here. Also, the C++ should be removed, right? I don't think that the services are available for C++"   by dmagda View feedback http