Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions client-sdks/advanced/attachments.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -2149,7 +2149,7 @@ var queue = new AttachmentQueue(new AttachmentQueueOptions
### Transferring Large Files Without Buffering

<Note>
This section applies to React Native, Expo and Node.js platforms only, and requires `@powersync/react-native` v2.0.3 or `@powersync/node` v0.21.0 or later. React Native also requires `@powersync/attachments-storage-react-native` v0.1.0 or later.
This section applies to React Native, Expo and Node.js platforms only, and requires `@powersync/react-native` v2.1.0 or `@powersync/node` v0.21.0 or later. React Native also requires `@powersync/attachments-storage-react-native` v0.1.0 or later.
Comment thread
khawarizmus marked this conversation as resolved.

In the Dart and Kotlin SDKs, the remote storage interface is already stream-based (`Stream`/`Flow`), so transfers can avoid buffering. The Swift SDK currently receives files as `Data` and has no streaming equivalent yet.
</Note>
Expand Down Expand Up @@ -2230,7 +2230,7 @@ async function attachRecording(localUri: string, recordingId: string) {
### Custom Transport Adapters

<Note>
The transport API requires `@powersync/web` v2.2.0, `@powersync/react-native` v2.0.3, or `@powersync/node` v0.21.0 or later. React Native also requires `@powersync/attachments-storage-react-native` v0.1.0 or later.
The transport API requires `@powersync/web` v2.2.0, `@powersync/react-native` v2.1.0, or `@powersync/node` v0.21.0 or later. React Native also requires `@powersync/attachments-storage-react-native` v0.1.0 or later.
</Note>

In the JavaScript SDKs, you can also write your own [transport adapter](#transferring-large-files-without-buffering). A custom remote storage adapter always receives the file as one full in-memory buffer. A custom transport receives the file's path instead. This makes the following possible:
Expand Down
Loading