![]() ![]() This means you can make a simple single-event-driven app with much less work - for example, an app that tracks reacji (Slack’s emoji reactions) only requires subscribing to reaction_added or reaction_removed. Instead of an endless stream of data, the Events API allows you to subscribe to only the events required for your app, delivered to you via HTTP. If the RTM API is a fire hose, the Events API is a watering can - easy to wield and useful. The Events API, on the other hand, is a tidy way to build with simplicity and scalability in mind. Slack is built with the RTM API, so it’s not going anywhere, but the RTM API usually provides too much data and too many websockets for developers to manage in a pleasant, productive way. The RTM API opens a websocket for every team connected and gives developers a fire hose of data. Previously, the only way to make apps that respond to activity outside of Slash Commands or Message Buttons was to use the RTM API. The Events API is a new way to build apps that respond to activity as it happens, in Slack. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |