Hi, I'm currently working on a website in which there is some content generated by users. In this case the user can store some of his profile. He then receives a link via email with a link which enables him to access the profile instantly.
The main problem I'm having is because of the architecture... the environment on which this occurs consists of two public instances (preceded by a load balancer). When a user stores his profile it will exists only on one public instance. The next time he wants to access the profile it is not guaranteed he will be on the same server as the one he stored his profile on. What is the usual/common/best way to deal with this kind of problems? I can think of the following solutions: 1) Store the profile on the authoring server and publish it using an automatic workflow 2) Store it on one public server and sync it to the other 3) Store the profile in a custom database and access this from both public servers Choice number 3 is the most easy one, but then we cannot use the user interface of Magnolia to access the profile anymore since it will not be stored in the JCR anymore. For the other 2 options... I have no idea if and (absolutely no idea) how to implement this. Can someone give me some pointers/directions/ideas on how to solve such an issue? -- View this message in context: http://www.nabble.com/Sharing-data-over-public-instances-tp20108329p20108329.html Sent from the Magnolia - User mailing list archive at Nabble.com. ---------------------------------------------------------------- for list details see http://www.magnolia-cms.com/home/community/mailing-lists.html ----------------------------------------------------------------
