NodeConfiguration confusion

[TryingAnotherOn]

In my application changes are sent to others by a node and
those changes, once published to connected users, are no more
required on the cocomo serveries. So I set configurations for this
node as



changesNodeConfig = new NodeConfiguration();

changesNodeConfig.persistItems = false;



Although I have set presistItems false. During development
when I launch a new session for this application it receives
changes from previous session. It was kind of confusing then I
changed my settings to this



changesNodeConfig = new NodeConfiguration();

changesNodeConfig.persistItems = false;

changesNodeConfig.userDependentItems = true;



and it worked. I have read their description for these flags
in cocomo pdf document. Can anybody elaborate them a bit more. Are
these flags independent? and can we set them in combination
according to application needs?

[Former Community Member]

Hi,



These flags are independent. You can set them in any
combination depending on your needs. If you set
nodeConfig.userDependentItems= true , it means the message items in
this node depends on this particular user. When this user leaves
the room, this items in the node get retracted in the server. For
e.g. a user's audio or camera stream should be retracted once he
leaves a meeting room. The default value is false for
userDependentItems flag.



When you set persistItems = true in a node, the items remain
as long as that session in which it was created. It gets retracted
automatically on the server once the session ends. An example,
could be user notifications for various activities in a meeting
room.



In both the cases, you can also manually retract the
items.

[Former Community Member]

[Duplicate removed]

[Former Community Member]

Hi TAOH,



this does seem odd.. If you set persistItems as false, then
you should *never* see a sent message again, except at the time of
initial sending. You've either discovered a bug (which, we've used
persistItems before in ConnectNow, so I'm pretty sure it works), or
maybe the node didn't get set up as expected?



One thing I usually do at this point is check with the
CocomoDevConsole. If you look at that node in the Explore tab, is
everything set up as expected? If you uncheck UserDependentItems
(but keep persistItems false) do you get the same behavior? If so,
is it possible you've got some code which is sending messages as
the app starts up?



Let us know what you find, and we'll figure out what's up.

thanks

nigel