The chatroom provides developers with a set of lightweight in-room chat products. Compared to group mode, the chatroom is a more loose and open form, similar to a plaza. Users may freely join or leave, as there is neither a strict access mechanism nor a fixed member organization structure. Users can receive chatroom content upon joining, and cannot receive chatroom content after exiting.
Millions.
The chatroom server has a scalable, flexible structure design that has successfully supported millions of simultaneous online users in repeated tests. If an app developer has sudden need to hold a major event, they need only make a quick report to activate immediate capacity expansion.
Yes, it does.
Jocloud chatroom has global deployment capabilities, dividing the world into several regions and serving each independently. Developers can specify user access region with HMRSetChatRoomRegion to improve user experience.
No.
The chatroom does not provide user system and service data hosting services. User data—such as alias, portrait, and chatroom messages—are stored on the developer’s business server.
Currently, the chatroom supports string-type messages. A multimedia file can be uploaded to a cloud storage server; once a URL address is generated, you can send it to other members of the chatroom. Once other members receive the URL, the multimedia will load and display.
Currently, the chatroom supports Android, iOS, Windows (C++), and Web SDKs.
No. But developers can access Web SDK through Electron.
Currently, one-to-one private chat is supported within chatrooms, but not outside chatrooms.
Yes, it does.
There are two types of user attributes available for use in the chatroom:
No.
Chatroom-configured user attributes are only valid within the current chatroom, and are cleared upon exiting. If a user re-joins the chatroom, their role will need to be reconfigured. To save chatroom and role attributes, the developer needs to record mapping relationships on their side.
Yes, it does.
Developers can use the Callback Authentication function to implement the encryption function of the chatroom. Set callback address in “User Center” After setting “callback authentication,” each time a user joins the chatroom, the chatroom server calls the business server to check user access permission.