ServiceManager Mobility, Proxy and Hybrid ----------------------------------------- Key: JBRULES-2361 URL: https://jira.jboss.org/jira/browse/JBRULES-2361 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: All Reporter: Mark Proctor Assignee: Mauricio Salatino Machines A B C ServiceManager (sm1) is deployed physically on A. With ksessions k1, k2, k3. C gets a remote connection to sm1 and starts working on k1. ServiceManager (sm2) is deployed physically on B. Seamless movement k1 is moved physically from sm1 to sm2. C needs to be able to seamlessly keep working k1, unaware of the move. Seamless proxy B gets remote connection to k2 on A's SM1. B registers k2 in sm2. If C was to lookup sm2.k2 it would be talking via a proxy, via B to C. Hybrid C decides that it needs to move k1 locally for continued work. Currently it only has a remote sm1. k1 should stayed regestered on sm1, but once moved locally to C it would effectively proxy from A to C. If k1 is on C, have we made a "sm1" that is partially natively on A and partially natively on C? This is almost like a clustered sm.... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira