#Fastest way to communicate between webview and Rust backend
20 messages · Page 1 of 1 (latest)
@valid oyster thanks -- do you know if there's any performance drawback to having MANY channels?
i have many lists of... things. and i'm wondering whether to make one channel per list, or one per thing
as per Tauri docs
it might not be suitable to sending a large amount of data.
looking through the issues on github, i don't seem to find any issues related to having many channels
another option could be to have custom URI protocol
this shouldn't be a problem i think
i think that shouldn't really be much faster than using channels right? tauri itself shouldn't add a lot of overhead to tauri::ipc responses
oh wait what, actually it seems like channels are using webview.eval too?
one channel per thing would be logical but that also depends
maybe there's any way I can webview.eval myself
but i wonder why they then say that channels are faster than events?
they say events eval, and channels are faster
serialization
seems like that's the only difference