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
In section 7, which outlines HTTP based interaction, the server stores its consent request in a JSON file. Why not use this JSON file also in Javascript based interactions?
Many websites would want to access ADPC on both client and server side. It would be inconvenient having to use 2 separate mechanism to send requests in each case.
The text was updated successfully, but these errors were encountered:
We indeed discussed the option of simply passing the URL of the JSON file to the JavaScript API. However, this seems quite contrary to existing APIs, limits the flexibility of JS (e.g. asking consent while offline?), and there seems no need for it because the website can simply fetch the JSON file itself with two extra lines of code:
In section 7, which outlines HTTP based interaction, the server stores its consent request in a JSON file. Why not use this JSON file also in Javascript based interactions?
Many websites would want to access ADPC on both client and server side. It would be inconvenient having to use 2 separate mechanism to send requests in each case.
The text was updated successfully, but these errors were encountered: