Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Agenda Request - HTTP API #205

Open
martinthomson opened this issue Nov 28, 2024 · 2 comments
Open

Agenda Request - HTTP API #205

martinthomson opened this issue Nov 28, 2024 · 2 comments
Assignees
Labels
agenda+ Request to add this issue to the agenda of our next telcon or F2F

Comments

@martinthomson
Copy link
Contributor

Agenda+: Attaching API calls to HTTP exchanges

One of the key items we identified as a likely essential extension to a core attribution API was the ability to have the API invoked as a side effect of ordinary HTTP requests. That's how the business operates today with its pixels and whatnot.

Things get a little gross when you want to have the browser generate responses to requests from servers, so you end up with API requests being carried in HTTP responses and API responses being carried in subsequent HTTP requests. But if we hold our noses for long enough to get over that, it's possible to build something that isn't too offensive... I think.

We've some sketches of how this might work with our current API. We hope to have more fully developed proposals to share before we meet.

Time

20-30 minutes.

Links

@martinthomson martinthomson added the agenda+ Request to add this issue to the agenda of our next telcon or F2F label Nov 28, 2024
@AramZS
Copy link
Contributor

AramZS commented Dec 9, 2024

Added to the agenda for day 1! https://github.com/patcg/meetings/pull/209/files

@martinthomson
Copy link
Contributor Author

Presentation and initial pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
agenda+ Request to add this issue to the agenda of our next telcon or F2F
Projects
None yet
Development

No branches or pull requests

3 participants