Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • cameo cameo
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 43
    • Issues 43
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • CameoCameo
  • cameocameo
  • Issues
  • #97
Closed
Open
Issue created Oct 26, 2020 by yannick legoc@legocOwner

Remove server instances from API

The server instances are not easy to manage and in fact not very important.
We can imagine that the server instances are a pool managed implicitly.
This would help to have only one server instance per server and solve the server instance problem for connectToRequester().

We could imagine:

App app(name, endpoint)
App app(id, endpoint)

app.start()
app.connect()
app.stop();
app.waitFor();

Apps apps(name, endpoint) => the set of App
apps.kill();
apps.waitFor();

for (App app in apps) { use of key values to discriminate }

Q: Is it still interesting to be able to wait for a non-terminal state? A state handler would be more convenient. Q: However, what to do with a server that has no application instances anymore? Wait before terminating it (cf strategy for linked apps)

Edited Oct 26, 2020 by yannick legoc
Assignee
Assign to
Time tracking