Currently in the HTTP Webhook Profile every event must be sent in a separate HTTP request. For very frequent events or property readings (e.g. a temperature value that changes every second or less) this could quickly overwhelm a Consumer.
One mitigation to this problem could be to batch multiple events or property readings into a single event payload. This could be as simple as wrapping the event payload format in an array to include multiple events in the same payload.
Currently in the HTTP Webhook Profile every event must be sent in a separate HTTP request. For very frequent events or property readings (e.g. a temperature value that changes every second or less) this could quickly overwhelm a Consumer.
One mitigation to this problem could be to batch multiple events or property readings into a single event payload. This could be as simple as wrapping the event payload format in an array to include multiple events in the same payload.