Update to 4.0.0-alpha.3 - Response Engines, 'inject' the context.JSON/JSONP/Text/Data/Markdown/Render, Read HISTORY.md
## 4.0.0-alpha.2 -> 4.0.0-alpha.3
**New**
A **Response Engine** gives you the freedom to create/change the
render/response writer for
- `context.JSON`
- `context.JSONP`
- `context.XML`
- `context.Text`
- `context.Markdown`
- `context.Data`
- `context.Render("my_custom_type",mystructOrData{},
iris.RenderOptions{"gzip":false,"charset":"UTF-8"})`
- `context.MarkdownString`
- `iris.ResponseString(...)`
**Fix**
- https://github.com/kataras/iris/issues/294
**Small changes**
- `iris.Config.Charset`, before alpha.3 was `iris.Config.Rest.Charset` &
`iris.Config.Render.Template.Charset`, but you can override it at
runtime by passinth a map `iris.RenderOptions` on the `context.Render`
call .
- `iris.Config.IsDevelopment` , before alpha.1 was
`iris.Config.Render.Template.IsDevelopment`
**Websockets changes**
No need to import the `github.com/kataras/iris/websocket` to use the
`Connection` iteral, the websocket moved inside `kataras/iris` , now all
exported variables' names have the prefix of `Websocket`, so the old
`websocket.Connection` is now `iris.WebsocketConnection`.
Generally, no other changes on the 'frontend API', for response engines
examples and how you can register your own to add more features on
existing response engines or replace them, look
[here](https://github.com/iris-contrib/response).
**BAD SIDE**: E-Book is still pointing on the v3 release, but will be
updated soon.
2016-07-18 16:40:42 +02:00
|
|
|
package iris
|
|
|
|
|
|
|
|
import (
|
2016-09-01 05:01:53 +02:00
|
|
|
irisWebsocket "github.com/iris-contrib/websocket"
|
|
|
|
"github.com/kataras/go-websocket"
|
Update to 4.0.0-alpha.3 - Response Engines, 'inject' the context.JSON/JSONP/Text/Data/Markdown/Render, Read HISTORY.md
## 4.0.0-alpha.2 -> 4.0.0-alpha.3
**New**
A **Response Engine** gives you the freedom to create/change the
render/response writer for
- `context.JSON`
- `context.JSONP`
- `context.XML`
- `context.Text`
- `context.Markdown`
- `context.Data`
- `context.Render("my_custom_type",mystructOrData{},
iris.RenderOptions{"gzip":false,"charset":"UTF-8"})`
- `context.MarkdownString`
- `iris.ResponseString(...)`
**Fix**
- https://github.com/kataras/iris/issues/294
**Small changes**
- `iris.Config.Charset`, before alpha.3 was `iris.Config.Rest.Charset` &
`iris.Config.Render.Template.Charset`, but you can override it at
runtime by passinth a map `iris.RenderOptions` on the `context.Render`
call .
- `iris.Config.IsDevelopment` , before alpha.1 was
`iris.Config.Render.Template.IsDevelopment`
**Websockets changes**
No need to import the `github.com/kataras/iris/websocket` to use the
`Connection` iteral, the websocket moved inside `kataras/iris` , now all
exported variables' names have the prefix of `Websocket`, so the old
`websocket.Connection` is now `iris.WebsocketConnection`.
Generally, no other changes on the 'frontend API', for response engines
examples and how you can register your own to add more features on
existing response engines or replace them, look
[here](https://github.com/iris-contrib/response).
**BAD SIDE**: E-Book is still pointing on the v3 release, but will be
updated soon.
2016-07-18 16:40:42 +02:00
|
|
|
)
|
|
|
|
|
2016-09-09 07:09:03 +02:00
|
|
|
// conversionals
|
|
|
|
const (
|
|
|
|
// All is the string which the Emmiter use to send a message to all
|
|
|
|
All = websocket.All
|
|
|
|
// NotMe is the string which the Emmiter use to send a message to all except this websocket.Connection
|
|
|
|
NotMe = websocket.NotMe
|
|
|
|
// Broadcast is the string which the Emmiter use to send a message to all except this websocket.Connection, same as 'NotMe'
|
|
|
|
Broadcast = websocket.Broadcast
|
|
|
|
)
|
2016-09-01 05:01:53 +02:00
|
|
|
|
2016-09-09 07:09:03 +02:00
|
|
|
// Note I keep this code only to no change the front-end API, we could only use the go-websocket and set our custom upgrader
|
Update to 4.0.0-alpha.3 - Response Engines, 'inject' the context.JSON/JSONP/Text/Data/Markdown/Render, Read HISTORY.md
## 4.0.0-alpha.2 -> 4.0.0-alpha.3
**New**
A **Response Engine** gives you the freedom to create/change the
render/response writer for
- `context.JSON`
- `context.JSONP`
- `context.XML`
- `context.Text`
- `context.Markdown`
- `context.Data`
- `context.Render("my_custom_type",mystructOrData{},
iris.RenderOptions{"gzip":false,"charset":"UTF-8"})`
- `context.MarkdownString`
- `iris.ResponseString(...)`
**Fix**
- https://github.com/kataras/iris/issues/294
**Small changes**
- `iris.Config.Charset`, before alpha.3 was `iris.Config.Rest.Charset` &
`iris.Config.Render.Template.Charset`, but you can override it at
runtime by passinth a map `iris.RenderOptions` on the `context.Render`
call .
- `iris.Config.IsDevelopment` , before alpha.1 was
`iris.Config.Render.Template.IsDevelopment`
**Websockets changes**
No need to import the `github.com/kataras/iris/websocket` to use the
`Connection` iteral, the websocket moved inside `kataras/iris` , now all
exported variables' names have the prefix of `Websocket`, so the old
`websocket.Connection` is now `iris.WebsocketConnection`.
Generally, no other changes on the 'frontend API', for response engines
examples and how you can register your own to add more features on
existing response engines or replace them, look
[here](https://github.com/iris-contrib/response).
**BAD SIDE**: E-Book is still pointing on the v3 release, but will be
updated soon.
2016-07-18 16:40:42 +02:00
|
|
|
|
|
|
|
type (
|
2016-09-01 05:01:53 +02:00
|
|
|
// WebsocketServer is the iris websocket server, expose the websocket.Server
|
|
|
|
// the below code is a wrapper and bridge between iris-contrib/websocket and kataras/go-websocket
|
|
|
|
WebsocketServer struct {
|
|
|
|
websocket.Server
|
|
|
|
upgrader irisWebsocket.Upgrader
|
2016-10-09 20:09:53 +02:00
|
|
|
|
|
|
|
// the only fields we need at runtime here for iris-specific error and check origin funcs
|
|
|
|
// they comes from WebsocketConfiguration
|
|
|
|
|
|
|
|
// Error specifies the function for generating HTTP error responses.
|
|
|
|
Error func(ctx *Context, status int, reason string)
|
|
|
|
// CheckOrigin returns true if the request Origin header is acceptable. If
|
|
|
|
// CheckOrigin is nil, the host in the Origin header must not be set or
|
|
|
|
// must match the host of the request.
|
|
|
|
CheckOrigin func(ctx *Context) bool
|
Update to 4.0.0-alpha.3 - Response Engines, 'inject' the context.JSON/JSONP/Text/Data/Markdown/Render, Read HISTORY.md
## 4.0.0-alpha.2 -> 4.0.0-alpha.3
**New**
A **Response Engine** gives you the freedom to create/change the
render/response writer for
- `context.JSON`
- `context.JSONP`
- `context.XML`
- `context.Text`
- `context.Markdown`
- `context.Data`
- `context.Render("my_custom_type",mystructOrData{},
iris.RenderOptions{"gzip":false,"charset":"UTF-8"})`
- `context.MarkdownString`
- `iris.ResponseString(...)`
**Fix**
- https://github.com/kataras/iris/issues/294
**Small changes**
- `iris.Config.Charset`, before alpha.3 was `iris.Config.Rest.Charset` &
`iris.Config.Render.Template.Charset`, but you can override it at
runtime by passinth a map `iris.RenderOptions` on the `context.Render`
call .
- `iris.Config.IsDevelopment` , before alpha.1 was
`iris.Config.Render.Template.IsDevelopment`
**Websockets changes**
No need to import the `github.com/kataras/iris/websocket` to use the
`Connection` iteral, the websocket moved inside `kataras/iris` , now all
exported variables' names have the prefix of `Websocket`, so the old
`websocket.Connection` is now `iris.WebsocketConnection`.
Generally, no other changes on the 'frontend API', for response engines
examples and how you can register your own to add more features on
existing response engines or replace them, look
[here](https://github.com/iris-contrib/response).
**BAD SIDE**: E-Book is still pointing on the v3 release, but will be
updated soon.
2016-07-18 16:40:42 +02:00
|
|
|
}
|
|
|
|
)
|
|
|
|
|
2016-09-09 07:09:03 +02:00
|
|
|
// NewWebsocketServer returns an empty WebsocketServer, nothing special here.
|
|
|
|
func NewWebsocketServer() *WebsocketServer {
|
|
|
|
return &WebsocketServer{}
|
|
|
|
}
|
|
|
|
|
2016-09-01 05:01:53 +02:00
|
|
|
// Upgrade upgrades the HTTP server connection to the WebSocket protocol.
|
|
|
|
//
|
|
|
|
// The responseHeader is included in the response to the client's upgrade
|
|
|
|
// request. Use the responseHeader to specify cookies (Set-Cookie) and the
|
|
|
|
// application negotiated subprotocol (Sec-Websocket-Protocol).
|
|
|
|
//
|
|
|
|
// If the upgrade fails, then Upgrade replies to the client with an HTTP error
|
|
|
|
// response.
|
|
|
|
func (s *WebsocketServer) Upgrade(ctx *Context) error {
|
2016-10-09 20:09:53 +02:00
|
|
|
return s.upgrader.Upgrade(ctx.RequestCtx)
|
Update to 4.0.0-alpha.3 - Response Engines, 'inject' the context.JSON/JSONP/Text/Data/Markdown/Render, Read HISTORY.md
## 4.0.0-alpha.2 -> 4.0.0-alpha.3
**New**
A **Response Engine** gives you the freedom to create/change the
render/response writer for
- `context.JSON`
- `context.JSONP`
- `context.XML`
- `context.Text`
- `context.Markdown`
- `context.Data`
- `context.Render("my_custom_type",mystructOrData{},
iris.RenderOptions{"gzip":false,"charset":"UTF-8"})`
- `context.MarkdownString`
- `iris.ResponseString(...)`
**Fix**
- https://github.com/kataras/iris/issues/294
**Small changes**
- `iris.Config.Charset`, before alpha.3 was `iris.Config.Rest.Charset` &
`iris.Config.Render.Template.Charset`, but you can override it at
runtime by passinth a map `iris.RenderOptions` on the `context.Render`
call .
- `iris.Config.IsDevelopment` , before alpha.1 was
`iris.Config.Render.Template.IsDevelopment`
**Websockets changes**
No need to import the `github.com/kataras/iris/websocket` to use the
`Connection` iteral, the websocket moved inside `kataras/iris` , now all
exported variables' names have the prefix of `Websocket`, so the old
`websocket.Connection` is now `iris.WebsocketConnection`.
Generally, no other changes on the 'frontend API', for response engines
examples and how you can register your own to add more features on
existing response engines or replace them, look
[here](https://github.com/iris-contrib/response).
**BAD SIDE**: E-Book is still pointing on the v3 release, but will be
updated soon.
2016-07-18 16:40:42 +02:00
|
|
|
}
|
|
|
|
|
2016-09-09 07:09:03 +02:00
|
|
|
// Handler is the iris Handler to upgrade the request
|
|
|
|
// used inside RegisterRoutes
|
|
|
|
func (s *WebsocketServer) Handler(ctx *Context) {
|
2016-10-09 20:09:53 +02:00
|
|
|
// first, check origin
|
|
|
|
if !s.CheckOrigin(ctx) {
|
|
|
|
s.Error(ctx, StatusForbidden, "websocket: origin not allowed")
|
|
|
|
return
|
|
|
|
}
|
|
|
|
|
|
|
|
// all other errors comes from the underline iris-contrib/websocket
|
2016-09-09 07:09:03 +02:00
|
|
|
if err := s.Upgrade(ctx); err != nil {
|
|
|
|
if ctx.framework.Config.IsDevelopment {
|
|
|
|
ctx.Log("Websocket error while trying to Upgrade the connection. Trace: %s", err.Error())
|
|
|
|
}
|
2016-10-09 20:09:53 +02:00
|
|
|
|
|
|
|
statusErrCode := StatusBadRequest
|
|
|
|
if herr, isHandshake := err.(irisWebsocket.HandshakeError); isHandshake {
|
|
|
|
statusErrCode = herr.Status()
|
|
|
|
}
|
|
|
|
// if not handshake error just fire the custom(if any) StatusBadRequest
|
|
|
|
// with the websocket's error message in the ctx.Get("WsError")
|
|
|
|
DefaultWebsocketError(ctx, statusErrCode, err.Error())
|
|
|
|
|
2016-09-09 07:09:03 +02:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
// RegisterTo creates the client side source route and the route path Endpoint with the correct Handler
|
|
|
|
// receives the websocket configuration and the iris station
|
|
|
|
func (s *WebsocketServer) RegisterTo(station *Framework, c WebsocketConfiguration) {
|
2016-09-20 09:15:45 +02:00
|
|
|
|
2016-10-05 12:21:40 +02:00
|
|
|
// Note: s.Server should be initialize on the first OnConnection, which is called before this func when Default websocket server.
|
|
|
|
// When not: when calling this function before OnConnection, when we have more than one websocket server running
|
|
|
|
if s.Server == nil {
|
|
|
|
s.Server = websocket.New()
|
|
|
|
}
|
2016-09-20 09:15:45 +02:00
|
|
|
// is just a conversional type for kataras/go-websocket.Connection
|
2016-10-09 20:09:53 +02:00
|
|
|
s.upgrader = irisWebsocket.Custom(s.Server.HandleConnection, c.ReadBufferSize, c.WriteBufferSize, c.Headers)
|
2016-09-20 09:15:45 +02:00
|
|
|
|
|
|
|
// set the routing for client-side source (javascript) (optional)
|
2016-09-09 07:09:03 +02:00
|
|
|
clientSideLookupName := "iris-websocket-client-side"
|
2016-09-20 09:15:45 +02:00
|
|
|
station.Get(c.Endpoint, s.Handler)
|
2016-09-09 07:09:03 +02:00
|
|
|
// check if client side already exists
|
|
|
|
if station.Lookup(clientSideLookupName) == nil {
|
|
|
|
// serve the client side on domain:port/iris-ws.js
|
|
|
|
station.StaticContent("/iris-ws.js", contentJavascript, websocket.ClientSource)(clientSideLookupName)
|
|
|
|
}
|
2016-09-20 09:15:45 +02:00
|
|
|
|
|
|
|
s.Server.Set(websocket.Config{
|
|
|
|
WriteTimeout: c.WriteTimeout,
|
|
|
|
PongTimeout: c.PongTimeout,
|
|
|
|
PingPeriod: c.PingPeriod,
|
|
|
|
MaxMessageSize: c.MaxMessageSize,
|
|
|
|
BinaryMessages: c.BinaryMessages,
|
|
|
|
ReadBufferSize: c.ReadBufferSize,
|
|
|
|
WriteBufferSize: c.WriteBufferSize,
|
|
|
|
})
|
|
|
|
|
2016-10-09 20:09:53 +02:00
|
|
|
s.Error = c.Error
|
|
|
|
s.CheckOrigin = c.CheckOrigin
|
|
|
|
|
|
|
|
if s.Error == nil {
|
|
|
|
s.Error = DefaultWebsocketError
|
|
|
|
}
|
|
|
|
|
|
|
|
if s.CheckOrigin == nil {
|
|
|
|
s.CheckOrigin = DefaultWebsocketCheckOrigin
|
|
|
|
}
|
|
|
|
|
2016-09-20 09:15:45 +02:00
|
|
|
// run the ws server
|
|
|
|
s.Server.Serve()
|
|
|
|
|
2016-09-09 07:09:03 +02:00
|
|
|
}
|
|
|
|
|
2016-09-01 05:01:53 +02:00
|
|
|
// WebsocketConnection is the front-end API that you will use to communicate with the client side
|
|
|
|
type WebsocketConnection interface {
|
|
|
|
websocket.Connection
|
Update to 4.0.0-alpha.3 - Response Engines, 'inject' the context.JSON/JSONP/Text/Data/Markdown/Render, Read HISTORY.md
## 4.0.0-alpha.2 -> 4.0.0-alpha.3
**New**
A **Response Engine** gives you the freedom to create/change the
render/response writer for
- `context.JSON`
- `context.JSONP`
- `context.XML`
- `context.Text`
- `context.Markdown`
- `context.Data`
- `context.Render("my_custom_type",mystructOrData{},
iris.RenderOptions{"gzip":false,"charset":"UTF-8"})`
- `context.MarkdownString`
- `iris.ResponseString(...)`
**Fix**
- https://github.com/kataras/iris/issues/294
**Small changes**
- `iris.Config.Charset`, before alpha.3 was `iris.Config.Rest.Charset` &
`iris.Config.Render.Template.Charset`, but you can override it at
runtime by passinth a map `iris.RenderOptions` on the `context.Render`
call .
- `iris.Config.IsDevelopment` , before alpha.1 was
`iris.Config.Render.Template.IsDevelopment`
**Websockets changes**
No need to import the `github.com/kataras/iris/websocket` to use the
`Connection` iteral, the websocket moved inside `kataras/iris` , now all
exported variables' names have the prefix of `Websocket`, so the old
`websocket.Connection` is now `iris.WebsocketConnection`.
Generally, no other changes on the 'frontend API', for response engines
examples and how you can register your own to add more features on
existing response engines or replace them, look
[here](https://github.com/iris-contrib/response).
**BAD SIDE**: E-Book is still pointing on the v3 release, but will be
updated soon.
2016-07-18 16:40:42 +02:00
|
|
|
}
|
|
|
|
|
2016-09-01 05:01:53 +02:00
|
|
|
// OnConnection this is the main event you, as developer, will work with each of the websocket connections
|
|
|
|
func (s *WebsocketServer) OnConnection(connectionListener func(WebsocketConnection)) {
|
2016-09-09 07:09:03 +02:00
|
|
|
if s.Server == nil {
|
2016-10-05 12:21:40 +02:00
|
|
|
// for default webserver this is the time when the websocket server will be init
|
2016-09-20 09:15:45 +02:00
|
|
|
// let's initialize here the ws server, the user/dev is free to change its config before this step.
|
|
|
|
s.Server = websocket.New() // we need that in order to use the Iris' WebsocketConnnection, which
|
|
|
|
// config is empty here because are setted on the RegisterTo
|
|
|
|
// websocket's configuration is optional on New because it doesn't really used before the websocket.Serve
|
2016-09-09 07:09:03 +02:00
|
|
|
}
|
2016-09-01 05:01:53 +02:00
|
|
|
s.Server.OnConnection(func(c websocket.Connection) {
|
|
|
|
connectionListener(c)
|
Update to 4.0.0-alpha.3 - Response Engines, 'inject' the context.JSON/JSONP/Text/Data/Markdown/Render, Read HISTORY.md
## 4.0.0-alpha.2 -> 4.0.0-alpha.3
**New**
A **Response Engine** gives you the freedom to create/change the
render/response writer for
- `context.JSON`
- `context.JSONP`
- `context.XML`
- `context.Text`
- `context.Markdown`
- `context.Data`
- `context.Render("my_custom_type",mystructOrData{},
iris.RenderOptions{"gzip":false,"charset":"UTF-8"})`
- `context.MarkdownString`
- `iris.ResponseString(...)`
**Fix**
- https://github.com/kataras/iris/issues/294
**Small changes**
- `iris.Config.Charset`, before alpha.3 was `iris.Config.Rest.Charset` &
`iris.Config.Render.Template.Charset`, but you can override it at
runtime by passinth a map `iris.RenderOptions` on the `context.Render`
call .
- `iris.Config.IsDevelopment` , before alpha.1 was
`iris.Config.Render.Template.IsDevelopment`
**Websockets changes**
No need to import the `github.com/kataras/iris/websocket` to use the
`Connection` iteral, the websocket moved inside `kataras/iris` , now all
exported variables' names have the prefix of `Websocket`, so the old
`websocket.Connection` is now `iris.WebsocketConnection`.
Generally, no other changes on the 'frontend API', for response engines
examples and how you can register your own to add more features on
existing response engines or replace them, look
[here](https://github.com/iris-contrib/response).
**BAD SIDE**: E-Book is still pointing on the v3 release, but will be
updated soon.
2016-07-18 16:40:42 +02:00
|
|
|
})
|
|
|
|
}
|