Hi All,
>From what i understand the AF and SM are in different domains that is why distributed caching will not be able to handle this scenario right?. global cluster cache invalidation has been done with the use of a pub sub mechanism ( discussed in archi under "Global cluster cache invalidation code review Notes" ) but this will only be available in the next release AFAIK. Regards, Pulasthi On Tue, Nov 11, 2014 at 10:00 AM, Amalka Subasinghe <[email protected]> wrote: > > Hi, > > The scenario is, we have mounted SM's registry to the App Factory registry > to remove the remote call for read the resources. but still the write calls > happens via SM. see the image below. > > > > > The problem is, once we do a write call to the SM's registry, App Factory > registry cache won't get updated, so old information will be shown in App > Factory pages. > Is there a way to remove an entry from the App Factory registry cache when > we do a write call to the SM's registry? then when we do a read call, it > will load the cache again and show the updated information. > > Thanks > Amalka > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- -- Pulasthi Supun Software Engineer; WSO2 Inc.; http://wso2.com, Email: [email protected] Mobile: +94 (71) 9258281 Blog : http://pulasthisupun.blogspot.com/ Git hub profile: https://github.com/pulasthi
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
