the method of kick has a conflict of writing concurrently

[lopies]

another route write message with chan type,so the message response to client concurrent security,but the method of kick use basic connect to write to client, i can not use the method of kick to remove a person from room,it make a mistake about writing concurrent.

[lopies]

Session.Kick() ,method (s.entity.Kick(ctx)) ,click, implement by Agent.Kick(_, err = a.conn.Write(p)),it has a conflict

[lopies]

There is no solution to kicking people in the context of what he is sending a messagge if i am an administrator

[felipejfc]

you mean you can't kick someone if you're processing a handler that the player initiated?

[lopies]

you mean you can't kick someone if you're processing a handler that the player initiated?

First ,websocket connections cannot be written concurrently, the files push. Go and Kick. go, i think push.go(package app) is correct ,it uses Channel for security to send message to someone,but kick.go(app.go) uses the lowest level connection to send kick packet to someone,This is conflicting

[lopies]

you mean you can't kick someone if you're processing a handler that the player initiated?

I think ,the kick packet should use the type of channel defined earlier，you want to send kick packet to someone,maybe you can send a kick packet to chan,so there's no conflict.

[Tiper-In-Github]

I encountered the same problem