Nearby API Pre-Connection Phase
Nearby Connections API is one of the many APIs available in Google Play services.
This framework was introduced in early 2015.
Initially, it allowed only those devices to share data, which connected to the same wifi network.
After June 2017, in version 11.0, it also made use of Wifi hotspots, Bluetooth and BLE to provide offline communication support to the devices. https://goo.gl/QmB2zN #DataIntegration #ML
How and Why to Use an OAuth Proxy URL With Cloud Elements
#ICYDK: Ok, so that title should really read “Why and How…” since I plan on starting with the “Why” then moving to the “how”, but I don’t look backwards and neither should you. You’re an engineer and you have code to write, and I have a blog to write. So, off we go!
The Why
Some API providers only allow you to use a single callback URL when using an OAuth flow. Why? I haven’t the foggiest of ideas. That’s the route they decided to go, so Cloud Elements implemented a way for you to use a single callback to service multiple environments. Let’s say you have a single app for a Box integration your building. With that single app, you want to be able to hit both your testing and production environments. Well, out of the box (See what I did there) the provider does not allow that. So you can either spin up two apps, have environment variables in your code, and make a lot more work for yourself (Who has the time?). OR you can have one app with a proxy URL as the OAuth callback which has the ability to hit either environment. Your call, I’ll wait while you decide… https://goo.gl/aLTu77 #DataIntegration #ML
