Page MenuHomeSoftware Heritage

Use journal clients for webapp and deposit to subscribe to events
Open, NormalPublic


Now that we started using journal for the dag, we may have a need for more functional

Currently the webapp and the deposit needs to poll regularly information to update some

  • deposit status
  • save code now status

It'd be interesting to have dedicated topics for those so they can actually refresh
themselves out of a journal client. That would allow to drop the need for regular

Note: We may be able to use the existing topics (origin_visit_status for example) but
then the journal client would receive too much information that they would need to
filter out. Also poses the problem of eventual backfillings which could put too much
pressure on those dedicated journal clients (save code now today is only around 76k
origin requests...).