s3lph/multischleuder
1
0
Fork 0
Code Issues Pull requests Projects Releases 8 Packages Wiki Activity Actions

Failure Scenario: Same key used by multiple subscribers? #1

New issue
Closed
opened 2022-04-16 05:37:11 +02:00 by s3lph · 2 comments
s3lph commented 2022-04-16 05:37:11 +02:00 (Migrated from gitlab.com)
Copy link
  • Figure out whether Schleuder allows different subscribers to use the same key
  • Make sure a key is never deleted as long as it is still being used by another subscriber
- Figure out whether Schleuder allows different subscribers to use the same key - Make sure a key is never deleted as long as it is still being used by another subscriber
s3lph commented 2022-04-16 05:37:11 +02:00 (Migrated from gitlab.com)
Copy link

assigned to @s3lph

assigned to @s3lph
s3lph commented 2022-04-17 01:33:48 +02:00 (Migrated from gitlab.com)
Copy link

Schleuder does not permit this (only one subscription is kept), so any attempts to subscribe more than one user with the same key should be avoided.

Schleuder does not permit this (only one subscription is kept), so any attempts to subscribe more than one user with the same key should be avoided.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
fix-key-404
v0.1.9
v0.1.8
v0.1.7
v0.1.6
v0.1.5
v0.1.4
v0.1.3
v0.1.2
v0.1.1
v0.1
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: s3lph/multischleuder#1
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?