overview of casual command line interface

casual middleware has one entry point for all it’s administration, in a command named casual


In general the semantics of the casual CLI is:

$ casual <category group> <group specific options>...


To get an overview help for what options is possible use:

$ casual --help

To get detailed help for a specific category/option, use:

$ casual --help service

It’s possible to get detailed help for several categories/options at once:

$ casual --help service domain gateway

To see all possible help options use:

$ casual --help --help

help output

casual CLI shows the cardinality for the option it self and if the option takes values the cardinality of the values.

  • The cardinality of the option dictates the possible number of usages of that particular option. A common cardinality for an option is [0..1] -> zero-to-one usage (optional).

  • The cardinality of the values for an option dictates the number of values that particular option takes.



<option name> <cardinality>

--list-servers [0..1]

<option name> <cardinality> (<values>) <cardinality>

-restart-aliases [0..1]  (<alias>) [1..*]

notation example



zero to one


exactly 2 occurrences


two to infinity

[1..* {2}]

one to infinity. if more than 1, the step is 2. Possible occurrences: 1, 3, 5, ...

bash completion

casual provides bash-auto-completion on the command casual. Hence, it should help users to tab for guidance to appropriate options for their intention. Reducing the amount of options one needs to memorize.

unix friendly

casual aims to be as unix friendly as possible.

What do we mean with unix friendly?

  • Every human readable output to stdout should be parsable line by line, hence no composite information

  • Users should be able to combine other unix tools to achieve their goals (grep, sort, cut, |, etc…)

  • casual CLI commands should be as composable as possible


  • casual service --list-services | grep foo | less

  • casual service --list-services | sort -k6,7 | less


casual CLI uses colors in output default (can be altered with --color true/false). If casual CLI detects that stdout is not bound to a TTY (terminal), no colors will be produced. This to make it easier to combine casual CLI with other unix tools.


casual CLI has a few business related commands, such as queue --enqueue/--dequeue, call --service, transaction --begin/--commit, that could be used to solve real business problems.

These cli commands are annotated with ‘casual-pipe’ in the help.

These business related commands communicate with a non human readable ‘internal’ pipeline-protocol (binary) via stdout -> stdin, hence it’s possible to compose them.

The ‘causal-pipe’ has to be terminated to be able to consume stdout with cli commands that are not part of ‘casual-pipe’.

If casual detects that stdout is tied to a terminal casual will try to make it human readable


$ echo "some payload" | casual buffer --compose "X_OCTET/" | casual buffer --duplicate 2 | casual buffer --extract
  • casual buffer --compose "X_OCTET/" creates an X_OCTET/ buffer with the payload ‘some payload’ and send it downstream

  • casual buffer --duplicate 2 duplicates the buffer twice and send it downstream

  • casual buffer --extract extracts the payload of the buffer and sends it downstream, which is the terminal in this case.

    • If the payload is human readable, the output will be human readable.

host# casual transaction --begin \
 | casual queue --dequeue b2 \
 | casual call --service casual/example/echo \
 | casual queue --enqueue a2 \
 | casual transaction --commit
  • casual transaction --begin starts a transaction that will associate all actions with the transaction downstream

  • casual queue --dequeue b2 dequeues a message from b2 in transaction and send it downstream

  • casual call --service casual/example/echo calls service with payload from dequeue in transaction, the service reply is sent downstream.

  • casual queue --enqueue a2 enqueues the service reply to a2 in transaction

  • casual transaction --commit commits the transaction


If a transaction is used in the cli it’s paramount to terminate the transaction directive with casual transaction --commit or casual transaction --rollback. Otherwise the transaction(s) will never be committed/rolled back, and manually recovery is needed. The information/data will be safe and protected by the transaction semantics though, so no data will be lost.


A complete list of all categories and a brief description


Responsible for the current local domain. Scales servers and executables, and the lifetime of the domain.

See domain.operation.md


Responsible for all the services in the local domain.

See service.operation.md


Responsible for all inbound and outbound connections for the local domain.

See gateway.operation.md


Administration of transactions.

See transaction.operation.md


Administration for casual-queue.

See queue.operation.md


A generic XATMI service caller

See call.operation.md


A casual specific service describer

See describe.operation.md