First off, a thanks is in order - thanks for the excellent Websocket framework and excellent documentation/examples!

• I'm utilizing the framework's custom OnConnect function in my app.
• During this stage, the user has successfully initiated a websocket connection, and now I'm going to do some stuff.
• But what if something goes wrong? Instead of doing a log.Fatal on the whole server, it is obviously much better to just immediately terminate that specific websocket connection.

So, I tried to do something like this:

router.OnConnect(connOpen)

func connOpen(conn *ExtendedConnection, r *http.Request) {
    // Get the session (this may be an empty session)
    session, err := sessionStore.Get(r, sessionName)
    if err != nil {
        log.Error("Unable to get the session for HTTP request:", r)
        conn.Connection.Close() // This DOES NOT work
        return
    }

    // Get the username from the session
    username := session.Values["username"].(string)

    // Transfer the username from the session to a field in the ExtendedConnection for use later
    // conn.Username = username
}

However, this doesn't actually work - you can't close the connection from inside a OnConnect callback, because the connection hasn't actually started yet, as illustrated here in the source code: https://github.com/trevex/golem/blob/master/router.go#L137

How is this supposed to be done in the Golem framework?

Edit - I reworded the question and the example code so that it would be more clear.

Gary Burd's websocked implementation moved:
https://github.com/garyburd/go-websocket
to
https://github.com/gorilla/websocket

As it stands, golem is not flexible enough to handle some of the uses cases I had in mind, more specifically the ability to define some opaque data on the Connection for a chat application where I first authorize the connection
I do not want to re-authorize or cache this extra data (caching would involve having a global map[*Connection]mydata that I would need to protect from concurrent modification by different goroutines, and re-auth on every single event is wasteful)
If I missed a detail that makes this possible, please forgive me.

Hi, for example_connection_extension.go after refreshing page, I've got:

2014/07/29 09:43:11 http: panic serving 127.0.0.1:59175: reflect: Call with too many input arguments
goroutine 22 [running]:
net/http.func·011()
        /usr/local/go/src/pkg/net/http/server.go:1100 +0xb7
runtime.panic(0x61e1e0, 0xc208000ad0)
        /usr/local/go/src/pkg/runtime/panic.c:248 +0x18d
reflect.Value.call(0x6225e0, 0x763fb8, 0x0, 0x130, 0x6d7530, 0x4, 0xc208032500, 0x2, 0x2, 0x0, ...)
        /usr/local/go/src/pkg/reflect/value.go:475 +0x162c
reflect.Value.Call(0x6225e0, 0x763fb8, 0x0, 0x130, 0xc208032500, 0x2, 0x2, 0x0, 0x0, 0x0)
        /usr/local/go/src/pkg/reflect/value.go:411 +0xd7
github.com/trevex/golem.func·021(0xc208025080, 0xc2080284e0)
        /home/theaidem/work/golang/sandbox/websockets_ex/src/github.com/trevex/golem/router.go:301 +0x398
github.com/trevex/golem.func·012(0x7fb0574a6a08, 0xc2080503c0, 0xc2080284e0)
        /home/theaidem/work/golang/sandbox/websockets_ex/src/github.com/trevex/golem/router.go:138 +0x7cc
net/http.HandlerFunc.ServeHTTP(0xc208000380, 0x7fb0574a6a08, 0xc2080503c0, 0xc2080284e0)
        /usr/local/go/src/pkg/net/http/server.go:1235 +0x40
net/http.(*ServeMux).ServeHTTP(0xc208024690, 0x7fb0574a6a08, 0xc2080503c0, 0xc2080284e0)
        /usr/local/go/src/pkg/net/http/server.go:1511 +0x1a3
net/http.serverHandler.ServeHTTP(0xc208004300, 0x7fb0574a6a08, 0xc2080503c0, 0xc2080284e0)
        /usr/local/go/src/pkg/net/http/server.go:1673 +0x19f
net/http.(*conn).serve(0xc20804e300)
        /usr/local/go/src/pkg/net/http/server.go:1174 +0xa7e
created by net/http.(*Server).Serve
        /usr/local/go/src/pkg/net/http/server.go:1721 +0x313

I use golang-1.3
Any ideas, how to fix it?

First of all congratulations for this outstanding work.
I'm trying to use the session example (https://github.com/trevex/golem_examples/blob/master/example_session.go) but it isnt't working anymore. The validateSession is not finding the session defined by the loginHandler (https://github.com/trevex/golem_examples/blob/master/example_session.go#L23

I've tried to figure out what happened but I haven't get conclusions yet. I have tried with Chrome and Safari.

Any idea?

When settings extended connection its sensible to expect the same connection throughout the API like:

router.OnClose(func(conn *ExtendedConnection) {
})

but it doesn't work since the signature for OnClose expects *golem.Connection.

As the titled suggests 😄

Specifically given a *Connection object, is there a method that we can call on it that indicates to us that the *Connection object is still connected? Either a method or a struct variable, something that indicates that connection object is either still connected or not?

I would like to ask what is the test figures for these outcomes

1. connection with 1000 concurrent connections with open 65540 open files and unlimited processes
2. operate over 10 hours
3. see any race detections?