Use EventSource to push updates to clients

[wsanchez]

Use EventSource to push updates to clients.

[wsanchez]

Things to potentially push updates for:

• incidents
• personnel
• incident types
• incident reports

[wsanchez]

No way this will get done in the next three weeks, so punting.

[wsanchez]

Server now has a URI for data updates as of 22d0102

[wsanchez]

Dispatch queue subscribes to those events: c7fbe38

This reloads the entire queue data set after any update, so one question is whether that scales OK. It does appear that DataTables only does one GET request even though multiple update events come in, so that's a great thing.

[wsanchez]

Not done yet is having individual incident contexts update.

[wsanchez]

@kimballa: this is on the demo server.

Try opening the dispatch queue in one window, then open an incident in another. Change the incident's state or some other data visible in the dispatch queue and it should automatically update in the queue.

[wsanchez]

#110 for incident pages
#111 for incident types
#112 for personnel
#113 for incident reports

[wsanchez]

Closing this bug since the main server side feature is is place.

[kimballa]

Hmm. Sorry for getting to this late; it was a busy weekend of packing.

This "sort of" works for me. Creating an incident in a new tab, I see it show up in the dispatch queue. I then changed the incident description and it didn't update (for at least 10 seconds).

I refreshed the dispatch queue and it appeared correctly. I then tried to repeat this process, and loaded another new incident tab. This new description is not present.

I do see the default sorting, and the new incident updating URL, so thanks for getting those in there.

[wsanchez]

Well, poop. Chrome, right?

[kimballa]

da

On Tue, Aug 16, 2016 at 2:36 PM, Wilfredo Sánchez Vega <
notifications@github.com> wrote:

Well, poop. Chrome, right?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#46 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAFVUFzdLb4qSJZiulT58pcrrDLv9N84ks5qgi1UgaJpZM4Iowl7
.

[wsanchez]

OK I just pushed an update, though I don't think that should have fixed anything…

But I have Safari and Chrome open on my Mac and if I change an incident state or summary in Safari, I'm seeing the update in Chrome on both the Dispatch Queue and the open incident page (which this update added support for).

I've also tested updated coming to Safari.

Might need to debug non-Mac cases on site.

[kimballa]

Whether or not that should have fixed anything, I can no longer reproduce the failure. Looking good!

¯_(ツ)_/¯