id.net apis for hosts
TRANSCRIPT
![Page 1: id.net APIs for Hosts](https://reader035.vdocument.in/reader035/viewer/2022062412/58ed0f3d1a28ab52768b47af/html5/thumbnails/1.jpg)
id.net APIs for HostsHIGH LEVEL DISCUSSION ABOUT THE BEST WAYS TO USE ID.NET
![Page 2: id.net APIs for Hosts](https://reader035.vdocument.in/reader035/viewer/2022062412/58ed0f3d1a28ab52768b47af/html5/thumbnails/2.jpg)
Why use id.net?
o Prioritizing the userso Economies of scaleo Layered feature setso Growing the audience
![Page 3: id.net APIs for Hosts](https://reader035.vdocument.in/reader035/viewer/2022062412/58ed0f3d1a28ab52768b47af/html5/thumbnails/3.jpg)
TopologyWhat it looks like to use id.net
![Page 4: id.net APIs for Hosts](https://reader035.vdocument.in/reader035/viewer/2022062412/58ed0f3d1a28ab52768b47af/html5/thumbnails/4.jpg)
Client Side Only
![Page 5: id.net APIs for Hosts](https://reader035.vdocument.in/reader035/viewer/2022062412/58ed0f3d1a28ab52768b47af/html5/thumbnails/5.jpg)
Server Side Only
![Page 6: id.net APIs for Hosts](https://reader035.vdocument.in/reader035/viewer/2022062412/58ed0f3d1a28ab52768b47af/html5/thumbnails/6.jpg)
Mixed client and server side
![Page 7: id.net APIs for Hosts](https://reader035.vdocument.in/reader035/viewer/2022062412/58ed0f3d1a28ab52768b47af/html5/thumbnails/7.jpg)
Client Side VS. Server SideClient Server
Easy to implement Requires a server
Less secure More secure
Difficult to track Easier to monitor
Distributed Centralized
On demand Preloaded or fetched
![Page 8: id.net APIs for Hosts](https://reader035.vdocument.in/reader035/viewer/2022062412/58ed0f3d1a28ab52768b47af/html5/thumbnails/8.jpg)
Push Topology
![Page 9: id.net APIs for Hosts](https://reader035.vdocument.in/reader035/viewer/2022062412/58ed0f3d1a28ab52768b47af/html5/thumbnails/9.jpg)
Push VS. Pull
Push PullDifficult to implement Easier to implementServer side Server or client sideFaster updates Slow updates with long polling
Less resource intensive* More resource intensive*
![Page 10: id.net APIs for Hosts](https://reader035.vdocument.in/reader035/viewer/2022062412/58ed0f3d1a28ab52768b47af/html5/thumbnails/10.jpg)
What is Available?
SDKsoJavascriptoFlash (legacy)
LibrariesoOmniauth-idnetoOauth2 GemoSimple-oauth2oOauth-server-php
APIsoThe Oauth2 API setoSession API set (legacy)oThe old push APIoThe new push API
![Page 11: id.net APIs for Hosts](https://reader035.vdocument.in/reader035/viewer/2022062412/58ed0f3d1a28ab52768b47af/html5/thumbnails/11.jpg)
Push API
Application setting page on id.net
Response format JSON{ “data”: {}, “appid”: “123”, “pid”: “432”, “hash”: “sha256 sig”}
![Page 12: id.net APIs for Hosts](https://reader035.vdocument.in/reader035/viewer/2022062412/58ed0f3d1a28ab52768b47af/html5/thumbnails/12.jpg)
Conclusion
o Using id.net can help a platform growo Understanding the topology of client, server, and mixed networkso Client side and server side have many trade offso Exploring the current push APIs could add efficacies to a projecto There is still a strong use case for request/response pulling
![Page 13: id.net APIs for Hosts](https://reader035.vdocument.in/reader035/viewer/2022062412/58ed0f3d1a28ab52768b47af/html5/thumbnails/13.jpg)
What are your questions?
Ideas, comments, feedback