This trait is needed here because Tracker
is referentially transparent, and we leave it up for the emitters
to decide whether F
will be referentially transparent also.
Emitters are entities in charge of transforming events sent from tracker
into actual HTTP requests (IO), which includes:
+ Async/Multi-threading
+ Queuing EmitterPayload
+ Transforming EmitterPayload
into Bytes
+ Backup queue and callbacks
Trait for all acceptable Snowplow platforms
Tracker-specific self-describing JSON
Class for an event subject, where we view events as of the form Subject -> Verb -> Object
Tracker class
Tracker class
Sequence of emitters to which events are passed
Tracker namespace
ID of the application
Whether to encode JSONs
optionally a json containing the metadata context for the running instance
This trait is needed here because Tracker
is referentially transparent, and we leave it up for the emitters
to decide whether F
will be referentially transparent also.
Backward-compatibility