> The full path might be ann+camera@example.com/video.jpg, with the idea that every read of the file retrieves the most recent frame. Curious how this would wo

> The full path might be ann+camera@example.com/video.jpg, with the idea that every read of the file retrieves the most recent frame. Curious how this would work implementation-wise. Since the DirServer knows the file size (or at least has block descriptors), how would a custom StoreServer for the camera send back a dynamic-sized block? Would you define one block in the DirServer with a max size and allow the StoreServer to respond with a frame of any size below that max? Does the client validate the block sizes equate between the DirServer and StoreServer? Would the DirServer have to be "in on" the camera implementation alongside StoreServer for any of this to work?