HI Thanks for your response.
Actually I want to implement custom Thin Client Processor/Server which will process requests from multiple C++ thin Client which use TCP socket communication. The Client requests are to perform sql queries , cache gets and puts and Ignite Transaction operations. I have explored different options but they could not meet my requirements: 1. Ignite C++ : since there will be a lot of Clients and I'm restricted to use a separate Ignite C++ client node for each C++ Client since I need a separate Transaction context for each client, hence its memory intensive. Also there are some other issues which could not be reproduced/replicated here. 2. ODBC : since I need cache gets and puts operations and Transactions which are not supported currently and planned to be added in 2.5 version. Same with the case of Thin Client Protocol. Due to time constraint I want to try a custom Thin Client Processor where a new Thread is created for each client connection to process custom messages/requests and perform custom logic and appropriate operations on grid and send custom message/response.Also from a knowledge perspective I would like to know how Ignite processors work internally. -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
