You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All the "common patterns" assume a local proxy, i.e. they require a service running on a gateway. At least it looks that way... unless the local proxy is actually combined with the device.
Can there be a pattern where the device "registers" itself directly with a cloud service/remote proxy? In practice I think this pattern is quite common.
The text was updated successfully, but these errors were encountered:
To clarify, when I did the "register with a remote proxy" implementation, I actually set up a reverse tunnel to access the remote proxy; which in fact is a kind of local proxy. So maybe we just need to explain different ways to implement "local proxies".
Part of what I added to PR #176 addresses most of this, eg. when a local Servient acts as a client and connects to an external remote Servient to set up a tunnel.
Doing without a local proxy at all would require every device to support a tunneling protocol which is maybe NOT a good thing... more of an anti-pattern, really.
All the "common patterns" assume a local proxy, i.e. they require a service running on a gateway. At least it looks that way... unless the local proxy is actually combined with the device.
Can there be a pattern where the device "registers" itself directly with a cloud service/remote proxy? In practice I think this pattern is quite common.
The text was updated successfully, but these errors were encountered: