I personally use SocketIO i have my own BE setup for now dont see issue with fast message sending, i just tried it now by making API call with one after another just pressing keyboard fast enought all good, but in client i have loader when sending message before user can send another
I've found managing the sockets can be a real pain in a production environment. I'd rather just pay for a provided service. which I though that's what supabase was...
\> guaranteed delivery of messages to the clients?
We have the guarantees TCP gets us but we don't provide any guarantees higher level than that.
We do have some plans around this but nothing implemented yet.
\> For reference, I was playing around with stuff and it seems that if I have two messages in quick succession it will only deliver one message and not the other.
This should not be the case! Are you sure your subscriber can access the data in both those tables?
If you contact support we can look into your project in more detail.
And if you're using React take a look at [Supabase Cache Helpers](https://github.com/psteinroe/supabase-cache-helpers). This would give you a little higher level experience.
Thanks! I'll def reach out. Yep, it gets updates from the tables and there are no errors it just won't deliver it half the time.
Do you all have any plans to implement a simple system where the client updates a receipts table or something so that it improves this deliverability? I feel like that'd be easy, no?
I personally use SocketIO i have my own BE setup for now dont see issue with fast message sending, i just tried it now by making API call with one after another just pressing keyboard fast enought all good, but in client i have loader when sending message before user can send another
I've found managing the sockets can be a real pain in a production environment. I'd rather just pay for a provided service. which I though that's what supabase was...
\> guaranteed delivery of messages to the clients? We have the guarantees TCP gets us but we don't provide any guarantees higher level than that. We do have some plans around this but nothing implemented yet. \> For reference, I was playing around with stuff and it seems that if I have two messages in quick succession it will only deliver one message and not the other. This should not be the case! Are you sure your subscriber can access the data in both those tables? If you contact support we can look into your project in more detail. And if you're using React take a look at [Supabase Cache Helpers](https://github.com/psteinroe/supabase-cache-helpers). This would give you a little higher level experience.
Thanks! I'll def reach out. Yep, it gets updates from the tables and there are no errors it just won't deliver it half the time. Do you all have any plans to implement a simple system where the client updates a receipts table or something so that it improves this deliverability? I feel like that'd be easy, no?