Binary protocol for communication between instances of HaveClip

Possible conversations

Clipboard update

Requestor is sending ClipboardItem to replier.

1. Request: ClipboardUpdateReady
2. Reply: ClipboardUpdateConfirm
3. Request: ClipboardUpdateSend
4. Reply: Confirm

Serial clipboard

Begin serial mode

1. Request: SerialModeToggle
2. Reply: Confirm

End serial mode

1. Request: SerialModeToggle
2. Reply: Confirm

Add item to serial batch

1. Request: SerialModeAppendReady
2. Reply: ClipboardUpdateConfirm

Next step depends on status from reply:

• continue
  3. Request: ClipboardUpdateSend
  4. Reply: Confirm
• abort - close connection
• not exists / not matches
  • morph into conversation Copy serial batch
• not understood - close connection

Move to next item in serial batch

1. Request: SerialModeInfo
2. Reply: Confirm

Next step depends on status from reply:

• continue - close connection
• abort - close connection
• not exists / not matches
  • morph into conversation Copy serial batch
• not understood
  • morph into conversation Clipboard update

Restart serial batch

1. Request: SerialModeInfo
2. Reply: ClipboardUpdateConfirm

Next step depends on status from reply:

• ok - close connection
• not exists / not matches
  • morph into conversation Copy serial batch
• not understood
  • morph into conversation Clipboard update

Copy serial batch

1. Request: SerialModeInfo
   For each item command ClipboardUpdateSend
2. Reply: Confirm

Protocol structure

Message header

Message types

ClipboardUpdateReady

ClipboardUpdateConfirm

ClipboardUpdateSend

Confirm

SerialModeToggle

SerialModeAppendReady

SerialModeInfo