Skip to content

[Layer 5] How should acmp:price stay fresh — push or pull? #2

Description

@marc-poljak

Context. Layer 5 § Open Questions: "How are acmp:price fields kept up-to-date as market conditions change (push vs. pull)?"

A discovery manifest advertises a price. Compute prices move; a stale advertised price causes failed negotiations.

Your task. Compare the two models and any hybrid:

  • Pull: buyers re-fetch the manifest before negotiating (simple, but load + still stale between fetches).
  • Push: providers publish updates (fresher, but needs a channel + subscription).
  • How do real-world APIs with volatile prices (exchanges, ad exchanges, spot-instance markets) handle this?

Done = a comment or PR weighing the trade-offs against ACMP's principle of provider-agnostic simplicity (P3).

Metadata

Metadata

Assignees

No one assigned

    Labels

    good first issueGood for newcomersquestionFurther information is requestedwg-discoveryLayer 5 — Discovery (ARD binding) working group

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions