no buffering in the pipe. So upload throughput would be limited by download
time of the other client if you copy traffic using it, and vice versa.
If you fan out incoming traffic to multiple clients using MultiWriter,
throughput would be limited to the slowest client in the group, as there's
also no buffering in MultiWriter.
On Fri, May 9, 2014 at 3:14 AM, Sam Ghods wrote:
Yes, exactly what I was looking for. Crazy how much stuff is in the
standard lib. Thanks!
--
Sam
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
--Yes, exactly what I was looking for. Crazy how much stuff is in the
standard lib. Thanks!
On Fri, May 9, 2014 at 2:33 AM, Jesse McNelis wrote:
http://golang.org/pkg/io/#Pipe
Write() to one end of the pipe and give the other end of the pipe to
the http.Request.
If you need to write to many of these you can put the write end of the
pipe in a
http://golang.org/pkg/io/#MultiWriter
and write to that.
On Fri, May 9, 2014 at 5:57 PM, Sam Ghods wrote:
The only way to send a POST body using the http package seems to be by
assigning an io.ReadCloser to a new http.Request object. I could
implement a
ReadCloser that reads data off the file upload stream and feeds it to the
http client (or better yet, pass the original file upload Request.Body
directly into the new Request), but this doesn't work as well when I want to
duplicate the stream to multiple file servers with throttling and
monitoring
of the transfers.
You want,The only way to send a POST body using the http package seems to be by
assigning an io.ReadCloser to a new http.Request object. I could
implement a
ReadCloser that reads data off the file upload stream and feeds it to the
http client (or better yet, pass the original file upload Request.Body
directly into the new Request), but this doesn't work as well when I want to
duplicate the stream to multiple file servers with throttling and
monitoring
of the transfers.
http://golang.org/pkg/io/#Pipe
Write() to one end of the pipe and give the other end of the pipe to
the http.Request.
If you need to write to many of these you can put the write end of the
pipe in a
http://golang.org/pkg/io/#MultiWriter
and write to that.
--
Sam
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups "golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
