Identification
identification of cloud browser components
UC-1: Application needs to know how to identify
Description
- As an application i would like to know how to interpreted identification
- The cloud browser request geolocation
- cloud browser provides location of the orchestration
Identifications plays major role in QoE. it is used to provide the best know content available. However sometimes it could be confusing what part is identified. For example the geolocation api could be used to identify from which location the user is interacting. Based on this information different content could be served. However it should be unclear that the locations is based on the user location and not the cloud browser. This will also provide incorrect inside into analytic services. Usually the services are using the IP address as reference which may not work with a cloud browser (for example on a non IP or managed network infrastructure).
Actors
- client
- application
- cloud browser
Requirement
- there should be a convention how to interpreted identification APIs
note that where possible a cloud browser solution could provide a x-forwarded-for http header. The client type information could be obtained by the user agent string together with the cloud platform information.