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

PoC: Interface for Firebolt Privacy Module #332

Draft
wants to merge 9 commits into
base: master
Choose a base branch
from

Conversation

Karthick-Somasundaresan

No description provided.

@Karthick-Somasundaresan Karthick-Somasundaresan marked this pull request as draft February 26, 2024 13:57
@MFransen69 MFransen69 requested review from pwielders and MFransen69 and removed request for pwielders February 26, 2024 14:33
~IFireboltPrivacy() override = default;

// Pushing notifications to interested sinks
virtual uint32_t Register(IFireboltPrivacy::INotification* sink) = 0;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please use Core::hresult as return type, if you want to know why give me a call
(and of course do that for all methods below)


// @property
// @brief Provides Current resume watch status
// @alt:AllowResumePoints
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why @alt, is this an existing interface?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The method names in Firebolt spec are camelcased. In our thunder, all methods are made small. In the Thunder version that RDK has, @text is having an issue and is not changing the method name. Hence I used alt to achieve the same.

// @property
// @brief Provides Current resume watch status
// @alt:AllowResumePoints
virtual uint32_t AllowResumePoints(bool& allow /* @out */) const = 0;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As it mentions pointS what is the use case for this interface? Can there be multiple points?
If it it only for testing why not reuse another existing interface? Or is there really an existing use case?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In Firebolt, the property name is called AllowResumePoints along with 's' hence the name.


// @brief Set resume watch status
// @alt:SetAllowResumePoints
virtual uint32_t SetAllowResumePoints(const bool& value ) = 0;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

assuming the above and this method are a setter and getter (knowing the use case is helpful :) ) why is one a property and the other a method? (at least they should have the correct name and signature)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I read in the Thunder documentation that the properties should not do any other work other than just changing the property value. But in Firebolt, the expectation is that it has to update the cloud components and have to send that value change event. Hence made the setter as method and getter doesn't need any extra operation so made that as a property.

enum { ID = ID_FIREBOLT_PRIVACY };
enum StorageLocation : uint8_t {
Disk /* @text: Disk */,
InMemory /* @text: InMemory */,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No need to add the @text here, this is dthe default (PascalCase naming in JSON)

virtual Core::hresult AllowResumePoints(bool& allow /* @out */) = 0;
// @brief sets the current resume watch status
// @text:SetAllowResumePoints
virtual Core::hresult SetAllowResumePoints(const bool& value ) = 0;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oke to create both methods (i.s.o. properties) but please keep it consistent. Or both are prefixed with Get and Set or both are not prefixed (so no Get/Set in front of it).


// @property
// @brief Get the storage location
virtual Core::hresult GetStorageLocation(StorageLocation& value /* @out */) const = 0;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you remove Get/Set from the other methods remove it here as well for consistency.

Is there a "real" use-case for knowing where the configurations where stored ? Do we really need this method ?

Please explain the usecase .

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, there is no real usecase based on this. Since we are moving the configuration from the device-manifest file (ripple configuration) to plugin configuration, I thought if ripple wants to know the stored location for logging this API would be useful.


// @brief Provides Current resume watch status
// @text:AllowResumePoints
virtual Core::hresult AllowResumePoints(bool& allow /* @out */) = 0;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess this is the getter, why is it not const ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants