adding isAggregator flag

[mbaudis]

This commit adds an optional isAggregator flag to beaconResponseMeta which will allow especially aggregators to avoid duplications & loops.

[mbaudis]

... and this is a non-breaking addition so no delay necessary.

[redmitry]

Would it be better to put it in the beaconInformationalResponseMeta?
I mean that if the endpoint is an aggregator all its beaconResponseMeta are also isAggregator?

Other thing is to distinguish resultsets, but in this case it should be per resultset (ResultsetInstance)?

Dmitry

[mbaudis]

@redmitry Good point; added it to beaconInformationalResponseMeta in 4a6efe8

But it should also stay in the normal responses since otherwise it could only be accessed w/ multiple passes.

Resultsets: The idea is that all resultSets are treated equally; i.e. an aggregator will concatenate the ResultsetInstance objects from different Beacons in its resultSets. With that we don't introduce another layer or type of response. However, it would be helpful here to have some dedicated source parameter which indicates the originating beacon.

[redmitry]

it would be helpful here to have some dedicated source parameter which indicates the originating beacon.
Agree. Ideally it should contain the beacon identifier that originated the result set.
Something like "source": beaconId

[mbaudis]

@redmitry Like this 9ae6447 ?

[redmitry]

@redmitry Like this 3f25a45 ?

Yes