Today when any portion of a bestiary is updated, the front end POSTs the entire bestiary. For sub-objects, such as metadata, sharing, etc, we don't really need to do this. Correcting this will reduce payload sizes.
This came up as a user actually hit the 1Mb request size limit that Nginx enforces by default when trying to update the sharing on their bestiary. I increased the limit but this won't really scale.
Today when any portion of a bestiary is updated, the front end POSTs the entire bestiary. For sub-objects, such as metadata, sharing, etc, we don't really need to do this. Correcting this will reduce payload sizes.
This came up as a user actually hit the 1Mb request size limit that Nginx enforces by default when trying to update the sharing on their bestiary. I increased the limit but this won't really scale.