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
Current method for sending multimedia messages requires the content to be a file on the disk. I want it to be possible to send a multimedia message by passing it as a stream.
If you have 100 users who are sending 100mb files simultaneously, you have to buffer and save to fs all of that prior to sending it to weixin users. That is both inconvenient and hugely wasteful to resources if the media you are sending already comes as a stream.
During our conversation on 6/2/2018, Huan mentioned that in that case it might be impossible to guess the file mime and filename. I suggest following: in case if the stream object does not contain the common options properties like filename, contentType, and knownLenght, you can tell users to set them manually, or add additional options that will be read during MediaMessage creation.
The text was updated successfully, but these errors were encountered:
Current method for sending multimedia messages requires the content to be a file on the disk. I want it to be possible to send a multimedia message by passing it as a stream.
If you have 100 users who are sending 100mb files simultaneously, you have to buffer and save to fs all of that prior to sending it to weixin users. That is both inconvenient and hugely wasteful to resources if the media you are sending already comes as a stream.
During our conversation on 6/2/2018, Huan mentioned that in that case it might be impossible to guess the file mime and filename. I suggest following: in case if the stream object does not contain the common
options
properties likefilename
,contentType
, andknownLenght
, you can tell users to set them manually, or add additional options that will be read during MediaMessage creation.The text was updated successfully, but these errors were encountered: