Callbacks are now auto-instantiated by a thread that is listening for events from sliver. Each sliverapi payload should have a thread, though probably only 1 will ever be used at a time realistically. Currently doesn't support creating all of the callbacks when the service first starts up, but this would be easily implemented.
Callbacks are now auto-instantiated by a thread that is listening for events from sliver. Each sliverapi payload should have a thread, though probably only 1 will ever be used at a time realistically. Currently doesn't support creating all of the callbacks when the service first starts up, but this would be easily implemented.