After switching to Hazelcast, we rewrote the HTTP session replication to work with cluster messaging. However, this is suboptimal because we also have a proper caching implementation. So, session replication should happen via caching.
The way to implement this would be, for each HTTP session (UUID), there should be a cache in the respective tenant's space, under a single cache manager (HTTPSessionCacheManager, say). The cache should be created using the CacheBuilder API so that the HTTP session timeout is inline with the cache timeout. Now, session replication boils down to a matter of placing the relevant objects into this cache. This should be a simple implementation & would be good for a new person to take this up to learn more about Carbon concepts. You can talk to me if you need any clarifications. -- *Afkham Azeez* Director of Architecture; WSO2, Inc.; http://wso2.com Member; Apache Software Foundation; http://www.apache.org/ * <http://www.apache.org/>* *email: **az...@wso2.com* <az...@wso2.com> * cell: +94 77 3320919 blog: **http://blog.afkham.org*<http://blog.afkham.org> *twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> * linked-in: **http://lk.linkedin.com/in/afkhamazeez <http://lk.linkedin.com/in/afkhamazeez>* *Lean . Enterprise . Middleware*
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
