Hi Team, Could you please share your suggestions on the following:
- Storing session recordings directly in object storage (e.g., S3/MinIO) instead of the default local file system, without modifying the guacd (server) - The minimal, production-ready changes required in the Guacamole backend, such as the ideal hook point after the `.guac` file has been finalized - Whether there is any existing extension point, service, or architectural pattern in Guacamole that supports this use case - Any potential concerns or limitations with uploading the `.guac` file to object storage after `guacd` completes the recording The goal is to implement this in a maintainable, production-grade manner that aligns with Guacamole’s architecture — ideally via an extension or injectable service within the Java backend. Thanks and looking forward to your guidance. Thanks, Savinder Kaur
