I think we should do what Java client does -
add IgniteClientConfiguration.TransactionConfiguration, and get defaults
from there.
On Mon, Jul 6, 2020 at 11:57 PM Guru Stron <
[hidden email]>
wrote:
> Dear Igniters,
>
> I'm working on .NET thin client transactions and have the next question:
>
> What would be the best approach to handle defaults. Thick client handles it
> with a separate request (OP_CACHE_CONFIG_PARAMETERS) but I could not find
> any similar for thin ones. Is it ok for thin clients to handle defaults on
> "platform" side or should something similar to OP_CACHE_CONFIG_PARAMETERS
> be implemented?
>
> Thanks in advance!
>