yes, upload from client to server works with StreamingServer. For downloading big data from server to client, there are at least 5 options, each with their own pros and cons:
1. The replyStart-replyMore-replyFinish -combo supports sending response in parts. But it is naive in the sense that replyStart requires contentlength as parameter. 2. Http upload is symmetric to download, right? In that case it should be easy to write replyStartMultipart proc which sets appropriate headers and replyFinishMultipart proc which writes the boundary delimiter to the end. If this is what you need, open an issue. 3. Delivery of all static files should be done by your reverse proxy, which offers caching, compression, HTTP/3 and other sophisticated features that are not in the scope of an application-side web server. 4. Even if data is dynamic and/or private, it could be handled by reverse proxy using something like this: 1. when request for data arrives, write it to disk, optionally compress it, and give it a large random filename that is impossible to guess. Send this filename back to client. 2. client asks the file from reverse proxy which serves it as any static file. 3. after transfer is ready, client signals this (or after a timeout) and you can remove the file. 5. Send the data using websocket stream. Hope this helps.
