pply to most modern languages", he lists "Unhandled error
propagation is visible" as something not provided by C++ exceptions today.
It's possible that a decade from now, this will all have been a minor blip,
and you will eventually be proven right. But at the very least, this
c
ages, and which must originate in the same package. That
value seems worth prohibiting dot-imports. You occasionally have to deal
with things like "context.Context", but they are the exception not the rule
(there are more names in the io package alone than have been mentioned as
stutter
le of this), and then its all just registered in main()
generally using good old http.ServeMux for hostname-routing (perhaps
getting the hostname itself from a flag).
Sanjay
On Tuesday, December 19, 2017 at 1:14:18 AM UTC-8, rog wrote:
>
> > You strip whatever prefix you chose before
In the documentation for https://golang.org/pkg/net/#Conn, it's stated that
Multiple goroutines may invoke methods on a Conn simultaneously.
My guess is this is not meant to imply that it is necessarily safe to do
so. For instance, calls to Set*Deadline may create race conditions between
gorou
Hello Jan: Thanks for your prompt reply. Will try again. Will contact
author after that if unsuccessful. Yes, it is
https://github.com/mattn/go-oci8 - My inexpert guess is that there is
some problem with how git is installed in my Windows pc. Sanjay
On 2017-11-18 22:26, Jan Mercl wrote
, they seem a bit kludgy. Coming
from the Perl world, Go/oci8 does not look as easy as Perl/Oracle. Perhaps
I have not internalised the "Go way" as yet.
I am sending this hoping for help in oci8 installation. And for eventual
revamp of the package for easier installation.
Sanja
I suggest just using a self-signed cert for your LB<->appserver and
disabling cert-checking in your LB. Should be relatively straightforward;
you can even have your appserver generate a cert on startup, so there's
less messing around with files required.
It'll give you http2, and also cheaply p
