[Feature Request] Caching Integration #11
Description
Response data should be cached in several cases to prevent rate limitation, save resources and provide faster access. Caching should at least span over all data within a single Twitchery instance. Multi-instance support could also be an option by either providing a static caching solution, or a separate service.
Example: When a channel is requested, most of the data won't change during the objects lifetime, so they could be cached. Followers and subscribers are most likely to change. Data like this could be updated using events.
Another important thing to discuss: Should objects receive updates automatically, or should the user expect a fixed state? Right now, the Followers property on the Channel class uses injection to retrieve the most recent data when accessed - so it's something like a semi-fixed state at the moment and without caching at all.