search

Uninett / Howitz

1 stars 3 forks source link

Add mention of NTIE to readme #123

Closed hmpf closed 3 months ago

hmpf commented 3 months ago

Closes #111

codecov-commenter commented 3 months ago

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (main@900367c). Learn more about missing BASE report.

Additional details and impacted files ```diff @@ Coverage Diff @@ ## main #123 +/- ## ======================================= Coverage ? 48.60% ======================================= Files ? 16 Lines ? 1004 Branches ? 0 ======================================= Hits ? 488 Misses ? 516 Partials ? 0 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

github-actions[bot] commented 3 months ago

Test results

    4 files      4 suites   8s :stopwatch:   38 tests   38 :heavy_check_mark: 0 :zzz: 0 :x: 152 runs  152 :heavy_check_mark: 0 :zzz: 0 :x:

Results for commit 59e29d18.

hmpf commented 3 months ago

The description of NTIE is really brief. It could be expanded a little to give a very general overview of how NTIE update service works in Howitz ecosystem: from Howitz to Zino server.

Why? It's not relevant for running the service, only for devs. Implementation detail specific to protocol 1.

podliashanyk commented 3 months ago

The description of NTIE is really brief. It could be expanded a little to give a very general overview of how NTIE update service works in Howitz ecosystem: from Howitz to Zino server.

Why? It's not relevant for running the service, only for devs. Implementation detail specific to protocol 1.

I ment the overview to be that general that there is no need to go into implementation details or protocol specifics. Something as general as informing that every x seconds web client (Howitz) asks the web server (zinolib) whether the Zino server has sent notifications about any event updates.