Hi All, I am working on an improvement for Carbon to enable tomcat session replication support using caching .Our previous implementation was based on a Tomcat Valve ( CarbonTomcatSessionReplicationValve.java).And it was used to replicate the session and adding it to cluster message.
Http Session replication in carbon works like this (its quite similar to how the same work in a standalone tomcat). 1. Not every webbapp session will be replicated. You need to set a context property (distributable) for the webapp you need. 2. Once enabled, and when the session is modified on a node, that modification is sent to other nodes via a cluster message ( using clustering ) For the new implementation, initial suggestion is to use our caching implementation. So we need to store the session object in the cache and when session is modified, then we need to update the cache. Please guide me through the process what should I carried out and any references to help me further to achieve [1]. [1] https://redmine.wso2.com/issues/2816 -- *Pubudu Dissanayake* Software Engineer WSO2 Inc.; http://wso2.com lean.enterprise.middleware Mob: + 94 775 503 304 Blog: http://geekdetected.wordpress.com/ Linkedin: *http://lk.linkedin.com/in/pubududissanayake* <http://lk.linkedin.com/in/pubududissanayake> Flickr : https://www.flickr.com/photos/pubudufx/ Twitter: https://twitter.com/GeekInAction
_______________________________________________ Architecture mailing list Architecture@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
