On startup, the client makes some initial API calls and connects to a Message Server via WebSocket. The client starts with an empty model, which gets populated by a combination of local cache (as applicable) and API calls. * The Slack real-time messaging app works in web browsers, and our installable desktop app also uses a web-based view of the same hence, “Desktop” is an interchangeable term for both.
Members (humans and bots comprising your team).Channels (Public, Private, and Direct Messages).There are many elements to the model, but here are a few: The Slack desktop client* builds and maintains a data model for the duration of your session. This round of improvements went live in mid-2016, but as performance is a continuous area of focus, there are always more plans in the pipeline. Topic highlights include avoiding and deferring work, adding smart preloading capabilities, the pitfalls of LocalStorage, and lessons learned while refactoring. This two-part series is about our work refactoring part of the Slack desktop client for performance.
Whether doing magic with cards or a browser, it doesn’t hurt to have an ace up your sleeve. ♠️ Software performance is like a series of card tricks:
0 kommentar(er)
