SPIKE: Websockets

[jhansen-flexion]

As part of this weeks retro, we discussed that we should not (but do in some cases) use websockets in the project. IRS is not okay with the use of web sockets, so this causes a problem with our customer.

• [ ] Explore what to do about websocket use in the app, and what needs to change
• [ ] Explore options to use websockets and then gracefully degrade - is that adding unnecessary complexity to the app?
• [ ] Explore alternatives.
• [ ] Improve documentation or warnings not to use websockets somewhere that devs will catch it.

[jimlerza]

+1 for a modal that can't be dismissed that prevents a non-websocket-having user from interacting with any page containing a featured powered by websockets:

"This feature is unavailable to you. Please ask your IT administrator to enable websockets before proceeding."

Heck, we could even make the text "ask your IT administrator to enable websockets" a link that opens their mail client with a pre-populated message body: "To perform my duties, I need websockets enabled for *.ustaxcourt.gov." No "pretty please with sugar on top," just statement of fact.

Make it happen, IRS IT. Make it happen.

[TomElliottFlexion]

Possible solutions:

• Remove websockets entirely
• Failover
• Above comment

Questions:

• What percentage of users are able to use websockets?
• What work is being blocked?

[TomElliottFlexion]

Endpoint affected: update user info (for IRS)