Interface for components that should clean their state. Cleaning state most often is used during testing. But there may be situations when it can be done in production.
Interface for components that require explicit closure. For components that require opening as well as closing use IOpenable interface instead.
Interface for components that can be called to execute work.
Interface for components that can be asynchronously notified. The notification may include optional argument that describe the occured event.
Interface for components that require explicit opening and closing. For components that perform opening on demand consider using IClosable interface instead.
Interface for components that require execution parameters.
Helper class that cleans a stored object state.
Helper class that closes previously opened components.
Helper class that executes components.
Timer that is triggered in equal time intervals. It has a symmetric cross-language implementation and is often used by Pip.Services toolkit to perform periodic processing and cleanup in microservices.
Helper class that notifies components.
Helper class that opens components.
Contains a map with execution parameters. In general, this map may contain non-serializable values. And in contrast with other maps, its getters and setters support dot notation and are able to access properties in the entire object graph. This class is often use to pass execution and notification arguments, and parameterize classes before execution.