activationServerUri should not be specified manually #27

Open
opened 2025-11-10 02:56:58 +00:00 by raito · 1 comment
Owner

This is a major problem that we have to allocate a host/port on the developer system.

We should run gRPC over stdout/stdin pipes instead, logging should be part of the protocol.

This is a major problem that we have to allocate a host/port on the developer system. We should run gRPC over stdout/stdin pipes instead, logging should be part of the protocol.
Owner

I don't totally agree on the second part of your issue: having gRPC over HTTP is interesting because we could have:

  • a single server for multiple systems which are built and applied in parallel
  • a server which does not run on the client (so 1) if the client does not have enough ressource, arcana can be used; 2) it can run as a proxy or whatever)

BUT, I think we should use stdout/stdin when no activationServerUri is specified.

I don't totally agree on the second part of your issue: having gRPC over HTTP is interesting because we could have: - a single server for multiple systems which are built and applied in parallel - a server which does not run on the client (so 1) if the client does not have enough ressource, arcana can be used; 2) it can run as a proxy or whatever) BUT, I think we should use stdout/stdin when no `activationServerUri` is specified.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
arcana/arcana#27
No description provided.