N2c local notification evolution to support `hasMore`

Open
  • Is something wrong?
#17 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
haskell
Domain
distributed-systems, networking

Research direction

Start by reviewing the n2c notification mini-protocol and the related dmq-node issue #15. The payload identifies coordinated changes across the DMQ node, Pallas library, Mithril nodes and CIP; done means blocking requests expose hasMore and subsequent calls use non-blocking requests until hasMore is false.

Written by the indexing model from the issue text.

Description

enhancement

[!IMPORTANT]
This is an idea of enhancement. This will create a breaking change and require coordinated modifications of DMQ node, Pallas library, Mithril nodes and CIP.

Support the hasMore flag in the n2c notification mini-protocol blocking request to allow returning not the full list of messages available.
The process would be:

  • If the blocking request returns hasMore to true.
  • The next call made by the client is a non blocking request.
  • The previous steps repeats until the response includes hasMore to false.

This is related to the issue https://github.com/IntersectMBO/dmq-node/issues/15

Dominant language
Haskell
Stars
2
Forks
5
Avg merge
13h 24m
Merged PRs (30d)
4

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IntersectMBO/dmq-node

All issues in IntersectMBO/dmq-node

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.