Skip to content

Migrate from using port to use named pipes or socketfile #218

@ph

Description

@ph

The v1 protocol that we have today works over TCP port, with a higher quantity of services to be run by the Elastic Agent this will not scale easily and can cause conflict for already used port.

We should migrate our connection strategy to:

  • Named pipe under Windows
  • Sockerfile for macOS and Linux

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    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