I offered a PR on alice (which is a middleware library for the handlers)
that does that. It's essentially an application of the same pattern. We're
getting a lot of mileage for this.
https://github.com/justinas/alice/pull/40
On Tuesday, March 6, 2018 at 6:41:53 AM UTC-8, Eyal Posener wrote:
>
>
What do folks do in terms of managing/vetting dependencies and also hosting
them internally? In other language ecosystems, there are tools such as
Nexus or Artifactory that work as caching mirrors for binary dependencies.
That way, a company or a team can have a stronger control/governance on
d
It is actually with the latest (1.9.2). I'll file an issue.
Thanks.
On Tuesday, December 5, 2017 at 1:51:07 PM UTC-8, Dave Cheney wrote:
>
> Can you please check if this is happening with the current version of Go
> and if so raise a bug, https://golang.org/issue/new.
>
> Thanks
>
--
You rec
Mystery solved. It turns out it was coming from bytes.NewBuffer which was
being invoked in the method I listed. Somehow that was attributed to the
import line for bytes rather than the line of invocation.
On Tuesday, December 5, 2017 at 10:51:33 AM UTC-8, Dave Cheney wrote:
>
> No idea. Which ve
ecember 2017 12:09:54 UTC+11, Sangjin Lee wrote:
>>
>> A couple of questions on understanding go pprof's memory profile...
>>
>> When I list a certain function (with --alloc_objects), I see an
>> allocation number associated with an import line mysteriously. I am pr
A couple of questions on understanding go pprof's memory profile...
When I list a certain function (with --alloc_objects), I see an allocation
number associated with an import line mysteriously. I am pretty certain I
can rule out any source line offset. For example,
(pprof) list foo
Total: 5348
We enjoy using http.Transport as it gives us a real solid HTTP client
functionality and faithful protocol implementation. The connection
pooling/management is also bundled into http.Transport. That's the part I'd
like to discuss. The http.Transport connection management takes a stance on
a few
Hmm maybe I misunderstood your use case. I thought you were basically
setting a fixed write duration via SetWriteDeadline() before each Write()
call, in which case the same treatment probably should be done for Flush().
Sangjin
On Thu, Sep 14, 2017 at 3:33 PM, Juliusz Chroboczek wrote:
> > Is
Is extending the deadline right before flushing an option? If your deadline
is based on a relative duration, you could apply the same delay on Flush()
too because Flush() may incur write, no?
On Saturday, September 9, 2017 at 8:17:24 AM UTC-7, Juliusz Chroboczek
wrote:
>
> > bufio.Writer is abo
Is there a fast infoset encoding handler in go out there that can transform
it to and from a more textual (e.g. xml) format? I'm referring to the fast
infoset format that is used for some (old style) SOAP communication (see
https://en.wikipedia.org/wiki/Fast_Infoset). Google search doesn't turn
10 matches
Mail list logo
