Skip to content

Avoid global object pattern for apps #461

Description

@jlugao

Investigate: The current pattern to register jobs and create engine privileges creating a global object with the engine. The issue is that the session object could be subject to a race condition. I'm still not certain about this as session is passed as variable and not an attibute of the global object.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    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