Hi Danushka,
How does the secret is shared among nodes? is it by a configuration file
that is set in all nodes?
thank you.
On Fri, Sep 12, 2014 at 2:13 PM, Danushka Fernando danush...@wso2.com
wrote:
Hi All
In AF we are using mutual ssl authentcator which will login a provided
user to the
Hi Senka,
Even though the RXT configuration file it self is cached in the resource
cache. everytime load artifacts is called it will first do a db call to get
all the RXT types which in turn results in several more DB calls as it
seems. So we are trying to altogether stop DB calls from happening
Hi Maninda/Gihan,
Based on the offline discussions we had, your suggestions here seems to be
the ideal solution for our scenario. Since the payloads coming to EMM have
complex Json objects, writing a custom valve and extracting data doesn't
seem like a good option. We will have to extract data at
I presume you are using the listener API provided by javax.cache.
On Tue, Sep 16, 2014 at 11:47 AM, Pulasthi Supun pulas...@wso2.com wrote:
Hi Shariq,
Yes that is why we are using the cache. the cache will be distributed.
When node 1 changes the RXT it will flip the parity bit in the cache
Need to make this work with WSO2 security model
http://stackoverflow.com/questions/10057189/mqtt-security-how-to-prevent-abusers-subscribing-to-topics
Ramith add a redmine issue also.
--
Director, Research, WSO2 Inc.
Visiting Faculty, University of Moratuwa
Member,
Hi All,
I am currently working on the issue Redmine-3207[1].
*Issue:*
With the current notification impl, each node cache needs to sync with
every others. So when the particular resource updated, it gets the all
subscription keys from its cache and send notifications.
With the distributed cache,
