Improve ActivityPub delivery #252

Closed
opened 2018-10-01 18:19:38 +00:00 by elegaanz · 1 comment
elegaanz commented 2018-10-01 18:19:38 +00:00 (Migrated from github.com)

When sending activities to a lot of other inboxes, we currently have two problems:

  • some of them timeout, but blocks the delivery for a long time
  • if one request fails, the following ones are never sent

We should try to see if we can make each request asynchronously, and make handle errors properly to avoid to stop the other tasks.

Plume version (and/or commit): 0.2.0

When sending activities to a lot of other inboxes, we currently have two problems: - some of them timeout, but blocks the delivery for a long time - if one request fails, the following ones are never sent We should try to see if we can make each request asynchronously, and make handle errors properly to avoid to stop the other tasks. Plume version (and/or commit): 0.2.0

I think the second point was fixed in 4e6f3209, as part of replacing unwrap with error message without panic when no result was required. The first one can probably be implemented easily with reqwest::async, has it as now been stabilized

I think the second point was fixed in 4e6f3209, as part of replacing unwrap with error message without panic when no result was required. The first one can probably be implemented easily with reqwest::async, has it as now been stabilized
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
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: Plume/Plume#252
No description provided.