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 both connect to LCCS, will they be treated as two different users in LCCS world?
3) Sever to Server API impact on usage cost
Solved! Go to Solution.
Views
Replies
Total Likes
1) No need to subscribe from the server side for any of the S2S API. You just need to make sure the nodes exist.
2) Server sessions don't show up as users in the room (you are really doing asynchronous pushing of messages)
3) We are currently not charging for S2S calls or notification (we may change that in the future but for now we don't), but publishing messages will contribute to bandwidth and message usage.
Views
Replies
Total Likes
1) No need to subscribe from the server side for any of the S2S API. You just need to make sure the nodes exist.
2) Server sessions don't show up as users in the room (you are really doing asynchronous pushing of messages)
3) We are currently not charging for S2S calls or notification (we may change that in the future but for now we don't), but publishing messages will contribute to bandwidth and message usage.
Views
Replies
Total Likes
Thanks Raff.
Views
Replies
Total Likes
Views
Likes
Replies