search.go: cannot search logs from devices that have set netreceiver as host

[Saxon Milton]

For devices that have input pins and consequently require sensors to display these, we have their hosts set to netreceiver.appspot.com. However, some of these devices use the T0 pin to send logging. Netreceiver handles T pins by storing the datastore as binary data. Normally if we wish to view logs in the cloud, we use the vidgrind search UI. But this UI uses the Text entity, not the binary entity, so we cannot view the logs for the aforementioned devices. Eventually we’ll implement an equivalent signal and sensor type in vidgrind, but until then it would be nice to have a temporary solution to view logs that were stored as Binary entities by netreceiver. It is therefore proposed that the textHandler (which is called by the getHandler) which is called for T pins, can look at both Text entities and Binary entities. It would first check for Text with the specified ID, and if cannot find anything, then look at Binary with the specified ID.

[Saxon Milton]

Here is the issue re new Binary type. This will need to be dealt with first.

[Alan Noble]

FYI, has NetReceiver has a B(inary) type that was once used for audio data before we introduced the S(ound) type.

[Saxon Milton]

Merged in check-binarydata-for-logs (pull request #189)

test.go: getText now also checks for binaryData types with the mid and timestamp change in case netreceiver has put device logs here

resolves issue #178

Approved-by: Trek Hopton

→ <<cset 1a62d1b58010>>