Hi guys, was wondering if I can pick some brains.
There's tons of tutorials on how to implement "push notifications" on your web application using SignalR, but most/if not all requires some action to happen manually (like a controller being invoked by a user and/or a button click)
We have a list of records that needs to be printed, I need to show the number of records if any is available to the user. Once they print it, a print flag is set, making the number available to print, 0. This is specific to a user.
I've found a tutorial that uses sql broker and sqldependancy to notify when database changes occur, but that's not really what I am looking for.
Currently we're using the old way of setTimeout to poll the server constantly for any changes. I'm (obviously) trying to reverse that, saying that if there's any records TO print for a specific user, only notify them then.
Do you guys have any ideas on how I would implement something like that? Basically, when a client opens the website and logs in, they "subscribe" to the push notifications using their user ID. The server needs to somehow broadcast to that specific user ID that they have x number of records available to print.
I'm basically stuck at "how does the server send that push notifications without some kind of page reload or button being clicked"
Thanks
There's tons of tutorials on how to implement "push notifications" on your web application using SignalR, but most/if not all requires some action to happen manually (like a controller being invoked by a user and/or a button click)
We have a list of records that needs to be printed, I need to show the number of records if any is available to the user. Once they print it, a print flag is set, making the number available to print, 0. This is specific to a user.
I've found a tutorial that uses sql broker and sqldependancy to notify when database changes occur, but that's not really what I am looking for.
Currently we're using the old way of setTimeout to poll the server constantly for any changes. I'm (obviously) trying to reverse that, saying that if there's any records TO print for a specific user, only notify them then.
Do you guys have any ideas on how I would implement something like that? Basically, when a client opens the website and logs in, they "subscribe" to the push notifications using their user ID. The server needs to somehow broadcast to that specific user ID that they have x number of records available to print.
I'm basically stuck at "how does the server send that push notifications without some kind of page reload or button being clicked"
Thanks