Re: Is there limitation on Semaphores and Queues?

Anatoly, Please properly subscribe to the user list (this way we will not have to manually approve your emails and you will get answers on your questions quicker). All you need to do is send an email to “ user-subscr...@ignite.apache.org” and follow simple instructions in the reply Since the cont

Re: Node.js features

Node.JS should be supported as part of 1.6. I am not sure about continuous queries, but would be nice to have this supported. Andrey Gura, can you please comment here? D. On Thu, Jan 7, 2016 at 6:37 PM, ignite_mk wrote: > I see some activity on node.js integration as part of 1.6 release. > Is

Re: Web app with CMS

Hi, Thanks, now I see the problem. Presently Ignite's web session filter doesn't support session ID renewal on its side. The filter, as you properly noted, just creates a new session from scratch every time it sees a new session ID. In any case I think that it's feasible to support session ID re

Re: Is there limitation on Semaphores and Queues?

Hi Anatoly, Does every system store the same content in the databases? I mean whether each database is just a replica of another or not? -- Denis -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Is-there-limitation-on-Semaphores-and-Queues-tp2415p2449.html Sent

Re: Issue with TcpDiscoveryJdbcIpFinder

Hi, Please properly subscribe to the user list (this way we will not have to manually approve your emails). All you need to do is send an email to “ user-subscr...@ignite.apache.org” and follow simple instructions in the reply. TcpDiscoveryJdbcIpFinder does check whether a table exists or not bef

Re: Error at cachequeryexample on withKeepBinary

Hi, Please properly subscribe to the user list (this way we will not have to manually approve your emails). All you need to do is send an email to “ user-subscr...@ignite.apache.org” and follow simple instructions in the reply. My guess is that you have a compilation error. Make sure that you're

Re: How asynchronous cache is implemented

Hi Antonio, Actually a cache related request goes this way: - first it gets to org.apache.ignite.internal.processors.cache.GridCacheIoManager; - after that it's transferred to org.apache.ignite.internal.managers.communication.GridIoManager which sends the request using one of TcpCommunicationS