You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If the size of the message payload exceeds the size limit for the configured transport, it would be neat if Rebus could automatically store the payload as an attachment, and then just send a message with an attachment ID.
This feature requires that Rebus can help with cleaning up old attachments, so this feature must be accompanied by #750 . This way, enabling this feature would require that some kind of clean-up strategy be defined, e.g. "clean up attachments that haven't been read for 72 hours", or something like that.
If the size of the message payload exceeds the size limit for the configured transport, it would be neat if Rebus could automatically store the payload as an attachment, and then just send a message with an attachment ID.
This feature requires that Rebus can help with cleaning up old attachments, so this feature must be accompanied by #750 . This way, enabling this feature would require that some kind of clean-up strategy be defined, e.g. "clean up attachments that haven't been read for 72 hours", or something like that.
This would also solve the issue described here.
The text was updated successfully, but these errors were encountered: