Devashish Dixit

Hi. The error code depends on the code that is returned by the server. Can you share some of your server code here?

Hi. This is already tested in the test cases: https://github.com/devashishdxt/tonic-web-wasm-client/blob/c89a136c1095c5a242334879cb3fdb32965ca04c/test-suite/simple/client/tests/web.rs#L79 I cannot suggest any meaningful solution for this unless I have a failing test full code which does not behave...

Closing this issue

> I see that this isn't currently building but would love to know if there are any already known blockers to using TLS with `tonic-web-wasm-client`. > > > > Awesome...

Hi. Another option is to not `await` the future returned by `add` in a loop. Instead, storing futures in a `Vec` and use something like `join_all` to await for all...

The way I understand this is that you're not waiting for value to be inserted in the database before yielding. You can have the same effect in current code by...

@FlippingBinary and @ShaddyDC. I'll look into it over the weekend. I anyway think that the API needs some restructuring for more ease-of-use.

@FlippingBinary I've experimented with a proc macro based API in [`deli`](https://crates.io/crates/deli). I'm still not entirely convinced with the proc macro based API as I think it is too opinionated. It'd...

Solving the bulk insert part is not that difficult. You can collect all the futures in a vec and join them in one go. I think that'll be much faster....

I've made some changes in latest version of `idb` crate which should enable faster bulk insertion. I'll soon port those changes to `rexie` too.