The hub doesn’t actually interpret the data. All non-discovery LAN socket traffic goes up to the cloud where the cloud looks for a valid HTTP frame to pass a whole response up to the device type. This allows a developer to handle the whole response in one ‘event’ rather than having to reconstruct the buffer or worse, not know if the whole frame was received or not.
The requests and responses aren’t size limited rather time limited to ~ 8 seconds for a whole request response transaction. If the Raw Socket flow was used, this RESTful timeout doesn’t apply.
Currently for this to work we are waiting on the RAW socket feature support to be added to the cloud. Hoping we get this out soon as well!