File Sharing
  • iOS : Objective-C
  • Android
  • Web
  • Electron
  • Windows
  • macOS
  • Overview
  • SDK Downloads
  • Demo APP
  • Sample Codes
  • Access Guide
  • Quick Starts
  • Scene Practices
  • Advanced Features
  • Error Codes
  • Server API
  • Documentation
  • File Sharing
  • Access Guide

Access Guide

Last updated:2022-03-22 13:06

This article mainly introduces the related API call sequence of ZegoDocsView SDK. With reference to this article, developers can have a preliminary understanding of the file sharing service process, which helps developers to access file sharing services more quickly.

1 File Sharing/Opening Process

  • ZegoDocsView SDK itself does not have the ability to simultaneously browse the local and remote ends. The signaling channel (referring to the local and remote communication channel) in the above flowchart can be the user's existing signaling channel. If Express SDK is used, Express SDK will provide in-room broadcast signaling channel function. For details, please refer to Real-time Message.
  • The instant file sharing service provides a test environment and a production environment. Files in different environments are isolated from each other and cannot be accessed. Please pay attention when accessing development.
  • ZEGO also provides an interactive whiteboard SDK, which can be used with ZegoDocsView to realize multi-person real-time whiteboard interaction, document annotation and other functions.

The file sharing service provides two ways to upload and transcode files in response to possible situations for developers:

  1. Upload the online file at the specified address through the server-side API (which can be on the developer's own cloud storage) to initiate transcoding. For details, please refer to Server API.

/Pics/docsview/docs_server1_en.png

  1. Upload a local file through the client SDK API to initiate transcoding.

/Pics/Android/Docsview/docs_sdk_android_en.png

Page Directory