id.net APIs for Hosts

id.net APIs for HostsHIGH LEVEL DISCUSSION ABOUT THE BEST WAYS TO USE ID.NET

Why use id.net?

o Prioritizing the userso Economies of scaleo Layered feature setso Growing the audience

TopologyWhat it looks like to use id.net

Client Side Only

Server Side Only

Mixed client and server side

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

Push Topology

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*

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

Push API

Application setting page on id.net

Response format JSON{ “data”: {}, “appid”: “123”, “pid”: “432”, “hash”: “sha256 sig”}

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

What are your questions?

Ideas, comments, feedback