7 ms·
Or, if you’re building for clients with a traditional “enterprise” and “secure” IT infrastructure: add refresh buttons and call it a day. If there’s one thin
by rvanmil 3y ago
Or, if you’re building for clients with a traditional “enterprise” and “secure” IT infrastructure: add refresh buttons and call it a day.
If there’s one thing in my experience that consistently fails in these environments and cannot be fixed due to endless red tape, it’s trying to make real-time work for these type of clients.
- chgs 3y agoMy browser has a refresh button. Alas your application likely breaks when I use it.
- rvanmil 3y agoNot entirely sure why it would break…?
- klysm 3y agoclient side state that isn't in the URL or local storage
- chgs 3y agoClearly I don’t know what your application is, but many heavyweight “web apps” don’t cope with a simple refresh, kicking back to a default screen or even login screen in some cases.
- hobobaggins 2y agoSometimes this is to scope logins to single tabs for security reasons (I think that's why Userify does it that way). It's annoying but for infrequently used apps, no worse than getting logged out every three minutes.
- wruza 2y agoAlso some apps ignore simple refresh and only react to hard refresh (ctrl-f5 and alikes). Refresh is as unreliable as other methods from user pov.
- WuxiFingerHold 2y agoIn this threads context of sending specific application data from the server, I don't think this will happen.
- cbsmith 3y agoHonestly, all the techniques for this stuff have their problems, including the refresh button.
- rvanmil 3y agoTrue, though when carefully implemented it’s the most reliable option I guess.
- palmfacehn 2y agoJetty/CometD will fall back to long polling if other transports are not available.