Hrefna (DHC) @hrefna@hachyderm.io · activity timestamp 2 wk. ago Okay, let's fix this once and for all >_> Read more Read less Translate Translate alt #### Batch Endpoints One of the core features of featherpub is the concept of **batch endpoints**. What this means is that if you have an inbox: ``` /api/studios/{studio-id}/actors/{actor-id}/inbox ``` You can also expect it to have: ``` /api/studios/{studio-id}/actors/{actor-id}/inbox:batchCreate ``` In combination with the _studio actor_ maintaining the shared inbox, this allows one server to write: ``` /api/studios/{studio-id}/actors/default/inbox:batchCreate ``` To have a set of messages correctly routed, turning a $\theta(n)$ request pattern into a $\mathrm{O}(1)$ request. #### Batch Endpoints One of the core features of featherpub is the concept of **batch endpoints**. What this means is that if you have an inbox: ``` /api/studios/{studio-id}/actors/{actor-id}/inbox ``` You can also expect it to have: ``` /api/studios/{studio-id}/actors/{actor-id}/inbox:batchCreate ``` In combination with the _studio actor_ maintaining the shared inbox, this allows one server to write: ``` /api/studios/{studio-id}/actors/default/inbox:batchCreate ``` To have a set of messages correctly routed, turning a $\theta(n)$ request pattern into a $\mathrm{O}(1)$ request. Reply Boost Quote Like More actions Copy link Flag this post Block
alt #### Batch Endpoints One of the core features of featherpub is the concept of **batch endpoints**. What this means is that if you have an inbox: ``` /api/studios/{studio-id}/actors/{actor-id}/inbox ``` You can also expect it to have: ``` /api/studios/{studio-id}/actors/{actor-id}/inbox:batchCreate ``` In combination with the _studio actor_ maintaining the shared inbox, this allows one server to write: ``` /api/studios/{studio-id}/actors/default/inbox:batchCreate ``` To have a set of messages correctly routed, turning a $\theta(n)$ request pattern into a $\mathrm{O}(1)$ request. #### Batch Endpoints One of the core features of featherpub is the concept of **batch endpoints**. What this means is that if you have an inbox: ``` /api/studios/{studio-id}/actors/{actor-id}/inbox ``` You can also expect it to have: ``` /api/studios/{studio-id}/actors/{actor-id}/inbox:batchCreate ``` In combination with the _studio actor_ maintaining the shared inbox, this allows one server to write: ``` /api/studios/{studio-id}/actors/default/inbox:batchCreate ``` To have a set of messages correctly routed, turning a $\theta(n)$ request pattern into a $\mathrm{O}(1)$ request.
Hrefna (DHC) @hrefna@hachyderm.io · activity timestamp 2 wk. ago Technically the endpoint should be /api/studios/{studio-id}/v1/actors/{actor-id}. Read more Read less Translate Translate Reply Boost Quote Like More actions Copy link Flag this comment Block
Technically the endpoint should be /api/studios/{studio-id}/v1/actors/{actor-id}.