Closed ngwaitat closed 6 years ago
oops, 1. is a bug. Ready to be fixed in version 1.0.4-beta (during today Monday)
server.listLogin() always return only the currently logged in user. e.g. if I logged in 'tom' in Chrome and 'mary' in Firefox, Chrome side only report has 'tom' and Firefox side report only 'mary'. Should have both?
This behavior is correct. ListLogin() returns all the users logged in the same browser instance in different tabs, even they have been closed. You can think in this feature as in google, where you can have multiple sessions in the same browser and switch between them in different tabs of the same browser.
Is there a method returning the user ids that opened a particular collaborative object? getParticipants() I suppose returns the possible user ids that allow access that object, while listLogin() returns user ids that currently logged in regardless of which object opened. And would there be listener on the collaborative object when a user is opened/closed it?
No. I guess you mean to have a presence feature. It is planed in the short term roadmap.
Thank you very much!
Thank you for your answers :+1:
Uncaught (in promise) RangeError: Maximum call stack size exceeded
server.listLogin() always return only the currently logged in user. e.g. if I logged in 'tom' in Chrome and 'mary' in Firefox, Chrome side only report has 'tom' and Firefox side report only 'mary'. Should have both?
Is there a method returning the user ids that opened a particular collaborative object? getParticipants() I suppose returns the possible user ids that allow access that object, while listLogin() returns user ids that currently logged in regardless of which object opened. And would there be listener on the collaborative object when a user is opened/closed it?
Thank you very much!