16 สิงหาคม 2549 16:03
Recently I noticed that the Chat capability in Version 3.5 has problem. The chat capability is a Channel shared capability "[Capability.Channel(true)]", so, even the user who created the Chat leave the venue, as long as there still have other users in this venue, the Chat should still visible for them.
But as I tested, if the user who created the Chat leave, the Chat window will disappear, all other users in the venue could not see it.
I remember I didn't see this problem for Version 3.1 and 3.2.
Could someone confirm this?
- ย้ายโดย Max Wang_Chinasoft 28 เมษายน 2554 20:16 forum consolidation (From:Developer Discussions)
16 สิงหาคม 2549 16:41
OK, I see there is a configuration item on the config file to specify the capability is channel or not
<add key="MSR.LST.ConferenceXP.Capability.Chat.Channel" value="false"/>
After I change the value to true, the Chat became channel shared.
But as I tested, even if I set the value to false, the Chat capability somehow still does exists even the ower leave the venue.
30 สิงหาคม 2549 16:29
You have done good detective work. We changed the config file because we were tired of the channel behavior. It is kind of annoying for a capability to stick around so long.
The way a channel works, it stays alive as long as a participant is in the venue. Once all participants leave, the channel capability dies. The only place we were using this is chat, and we didn't really like it so we made it owned.
I am a little confused by your test results though. As you probably know, the config file only gets loaded at process start up. So you need to completely shut down CXP and restart the app in order to see your changes go into effect. Other than that, can you tell me which scenario does / and does not work correctly?