Guys, It looks like that if we need state on server side it is not REST anymore. We really need user sessions. Everything else you will invent here is just a hack.
Sergi 2015-11-05 1:31 GMT+03:00 Dmitriy Setrakyan <[email protected]>: > On Wed, Nov 4, 2015 at 2:46 AM, Yakov Zhdanov <[email protected]> wrote: > > > We can use IgniteUuid qryId = IgniteUuid.fromUuid(clientId); > > > > and restrict page requests for queries submitted from other clients. I.e. > > throw exception if qryId.globalId() != clientId > > > > Yakov, I think it is inconvenient to pass UUID in a query string. How about > we use node order, defined by ClusterNode.order() method? Essentially, > instead of passing just the queryID, REST client will also pass the > nodeOrder parameter. > > On the server side, we check that the received node order should be equal > to the local node order. If not, then error. This approach will have the > same behavior we do right now, and will also fix the bug mentioned by > Alexey. > > > > --Yakov > > > > 2015-11-04 12:21 GMT+03:00 endian675 <[email protected]>: > > > > > Alexey, > > > > > > No problem, here is a link that is relatively simple to understand : > > > > > > > > > http://javarevisited.blogspot.co.uk/2011/02/fix-protocol-session-or-admin-messages.html > > > > > > However, a simplified approach of just adding a client ID seems > > sufficient > > > - > > > the sequence number reset functionality of FIX is overly complex for > this > > > requirement. > > > > > > Regards > > > Mike > > > > > > > > > > > > -- > > > View this message in context: > > > > > > http://apache-ignite-developers.2346864.n4.nabble.com/HTTP-REST-sql-query-ID-problem-tp4524p4531.html > > > Sent from the Apache Ignite Developers mailing list archive at > > Nabble.com. > > > > > >
