Skip to content
This repository was archived by the owner on Apr 3, 2018. It is now read-only.

CL::Connection#subscribe is confusing as hell #3

@therealadam

Description

@therealadam

The ordering of the parameters in Connection#subscribe and in the service-side subscribe calls is incosistent. The names are confusing. The ordering as it appears in logging is confusing/inconsistent.

Make this better.

Everywhere a subscription is referenced, the names should indicate that events flow from left to right (sorry, RtL localities). That is, everywhere you see subscribe(a, b), it implies that events are published to a and fanned out to b.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions