This could be similar to Richard’s implementation or an existing @{557058:f36e7514-bbba-431e-8df0-3e3ac9a3395b} approach. We should wait on this until we exhaust our current processing/stacking options (i.e. they don’t prove sufficient for locating a given event).
Original report by me.
This could be similar to Richard’s implementation or an existing @{557058:f36e7514-bbba-431e-8df0-3e3ac9a3395b} approach. We should wait on this until we exhaust our current processing/stacking options (i.e. they don’t prove sufficient for locating a given event).