I think that in a lot of cases webhooks would work. That's what you use for instance_create, and it would works for processes like imports. We just need to know when the process is complete, and there's no real back and forth between us.
Not sure if that's easier since you have it in other places. There might be cases for websockets that I'm not thinking of too.
I read "constantly poll the server" and thought of where we do that, which is checking site copy status and import status. In that situation a webhook returning the single result would be the better option I think.
I understand what you mean though. Is this task is for custom use, like receiving updates on model data?
@mattwalter91 Push notifications are essentially socket connections, they are an always connected state to Apple or Google who then push something to the phone when needed. I used to work in finance and all our IoT devices or hardware terminals were connected via sockets in order to have faster processing, real time feedback, and the fact the end device could be behind unknown levels of networking. Basically if you got a connection there was nothing else to worry about.
Clickup and Google sheets etc all use websockets for the speed and realtime interaction with multi users....
Currently, the only way to handle asynchronous tasks is to constantly poll the server. We would like to be able to use WebSockets to enhance the user experience.
The text was updated successfully, but these errors were encountered: