Skip to content

Per-invocation customization of the underlying transport (HTTP) while still using ServiceCall abstraction #945

@artem-v

Description

@artem-v

Subj.

Current problems:

  • HTTP POST is hardcoded in HttpGatewayClientTransport.
  • Headers/query params are controlled globally by the transport, not per invocation.

Goals:

  • per-invocation customization of the underlying transport (HTTP) while still using ServiceCall abstraction, without breaking the correlation/encoding/decoding machinery.
  • Pass metadata inside ServiceMessage.headers.
  • real RESTful semantics (GET/POST/PUT) + per-call HTTP headers/query params while keeping ServiceCall architecture intact.

Something like:

serviceCall
  .requestOne(
     ServiceMessage.builder()
        .header("http.method", "GET")
        .header("http.header.X-Custom", "abc")
        .header("http.query", "limit=10")
        .data(payload)
        .build()
  );

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions