1) If server is not interested in receiving messages from LCCS, but it needs to push messages to clients using LCCS, does it need to subscribe to the collection node before calling publishItem? or it just need to login to LCCS account and call publishItem?2) if a client app and its server session bo...

We have noticed that          1)  Cocomo started disconnecting frequently, even when internet is working fine.           2)  When it is about to disconnect it hangs the app for sometime and then get disconnected.          3)  During startup(at login time) and reconnect(after getting disconnected) i...

This is a test case for the senario where clients computers proxy setting are not correct. In that case cocomo(lccs) should simply raise error after certain number of tries. I guess there might be an infinite loop bug in reconnect code that makes the app unresponsive.

I am testing my air application, that uses afcs, i guess air uses IE proxy settings on windows machine. For testing I unchcked proxy settings of IE to see afcs reconnect behavior, I run the application and found that it hangs when afcs try to reconnect.To narrow it down further I made a separate sam...

In my application users may have concurrent independent collaboration sessions. When a user starts a collaboration session, a new collection node is created, s/he subscribes to that collection node, sends invitation to participants (selective users) by a common collection node. My application needs ...

Although these features had already been requested in other posts, I am posting them again because I have been waiting for them for a long time. AFCS team can you please give any time frame when I would expect these.1. AFCS API should provide a way to configure collection nodes similar to 'nodes' pl...

Thanks for replyI have look at RootCollectionNode and found this removeNode(p_nodeName:String):voidRemoves the given node from this collection. This says it deletes 'node' not 'collection node'.

I am doing an app where there is a need for multiple (number is arbitrary) independent group chats. I first tried to solve this by using 'nodes' inside a single 'collection node' but found it does not scale, because every user is getting every message for each group regardless he is 'in' that group ...