Terracotta Discussion Forums (LEGACY READ-ONLY ARCHIVE)

Taylor. Thanks for the reply. Just wanted to confirm that clients are not pushed data by the terracotta server if they do not access it. So no network hogging for unneccessary data.

Sorry my QUESTIONS are as follows

6. How does Client 3 and Client 4 say that it needs changes to DSO_B and NOT changes to DSO_A

Thanks for the reply. My exact use case is as follows

1. I have 4 clients (Client 1 --- 4) connecting to a terracotta server

2. I want to share two different object roots (DSO_A , DSO_B)

3. Client 1 and Client 2 wants to see changes to the root object tree DSO_A

4. Client 3 and Client 4 wants to see changes to the root object tree DSO_B

QUESTIONS
**********

5. How does Client 1 and Client 2 say it needs only changes to DSO_A
and NOT changes to DSO_B

6. How does Client 3 and Client 4 say it needs only changes to DSO_B
and NOT changes to DSO_B

I came across reference to the fact that the terracotta servers pushes object changes only to those VM's where the object is resident.

I would like to know how I can indicate that a client is interested in changes only to a partiicular object. I noticed that the dso root section in the configuration XML applies to all the clients.

The way I say java.util.Date behaviou is that it was a field in a wrapper object. When I changed the date field, in the chane listener I say notification for the Date field getting changed and also the wrapper object getting changed. BTW the lock was on a method which had all these logic and not on the java.util.Date methods.

Is there a specific person I need to call in Professional Services ? Could I talk to u, since u are aware of my problem.

We have to support close to 100,000 concurrent connections and being a Gaming provider, the performance is very criticial.

I have 3 questions/observation :

1. The only issue i saw doing it myself is that by the time the change listener is called the master object is already modified, which means I have lost the original state. So I have to keep track of a copy object which represents the old state (maintained at the time the last push was done to the C++ client) and then every time I want to push the changes to the C++ client just compare every field in the master object with the copy object and then just push only those changes. I feel this will be too much CPU cycles.

2. Also would it be possible to engage your professional service team to provide us with any customization/hooks to ur code, which will allows us to identify the exact fields that were changed in any object.

3. Also I notiiced that if the change was to a Object (like a java.util.Date) vs a primitive type like int/string, it sends us the new changed object (java.util.Date) in the change listener handler. Any insights to this.

Thank for the prompt reply.

The windows client is written in MFC/Visual C++.

OS : Redhat Linux
JVM : JDK 1.5_06

I have been successful in doing some tests using Terracotta DSO. I have the following questions

1. I am able to get the changed object set through the Change Listener feature. Is there a way to even find which field in that object changed. For example I change say couple of strings in a object on one server. In the other server I want to be able to find which fields changed. The reason being that finally we need to push these changes to a windows client. So pushing the minimal data will immensely help reducing the bandwidth.

2. Do all the servers in a cluster need to be in a single LAN or could they be geographically spread.