Code Monkey home page Code Monkey logo

Comments (5)

Kavindu-Dodan avatar Kavindu-Dodan commented on August 15, 2024 4

I am also fine with language-specific implementations to handle the shutdown (context VS shutdown method).

After going through the spec, I think we should keep the keyword MUST and redefine the requirement to align with providers. Example suggestion,

The API MUST define a mechanism to propagate shutdown request to active providers

Also, requirement section ...must call the respective shutdown function on the active provider mismatch with the provider shutdown requirement [1], which is using the keyword MAY (contradict with must call as the provider might skip this)

The provider MAY define a shutdown function.... [1]


Altogether, if we agree on this, then we should correct both API & Provider spec sections to align.

[1] - https://github.com/open-feature/spec/blob/main/specification/sections/02-providers.md#25-shutdown

from spec.

weyert avatar weyert commented on August 15, 2024 1

I think that's reasonable

from spec.

thomaspoignant avatar thomaspoignant commented on August 15, 2024 1

Both solution are fine for me, but from the provider point of view it is always a bit tricky to have specificity for one language. I would prefer to have the same pattern everywhere.

If we want to go with the context approach I think we need to be extra cautious to make it explicit in the documentation how we expect providers to handle this.

from spec.

toddbaert avatar toddbaert commented on August 15, 2024 1

I am also fine with language-specific implementations to handle the shutdown (context VS shutdown method).

After going through the spec, I think we should keep the keyword MUST and redefine the requirement to align with providers. Example suggestion,

The API MUST define a mechanism to propagate shutdown request to active providers

Also, requirement section ...must call the respective shutdown function on the active provider mismatch with the provider shutdown requirement [1], which is uses the keyword MAY (contradict with must call as the provider might skip this)

The provider MAY define a shutdown function.... [1]

Altogether, if we agree on this, then we should correct both API & Provider spec sections to align.

[1] - https://github.com/open-feature/spec/blob/main/specification/sections/02-providers.md#25-shutdown

I like this proposal.

from spec.

Kavindu-Dodan avatar Kavindu-Dodan commented on August 15, 2024 1

@toddbaert this can be closed now as you already merged #193

from spec.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.