github.com/go-siris/siris (go): Package siris is a fully-featured HTTP/2 backend web framework written entirely in Google’s Go Language.  Source code and other details for the project are available at GitHub:  The only requirement is the Go Programming Language, at least version 1.8  Example code:  Access to all hosts that serve your application can be provided by the `Application#Hosts` field, after the `Run` method.  But the most common scenario is that you may need access to the host before the `Run` method, there are two ways of gain access to the host supervisor, read below.  First way is to use the `app.NewHost` to create a new host and use one of its `Serve` or `Listen` functions to start the application via the `siris#Raw` Runner. Note that this way needs an extra import of the `net/http` package.  Example Code:  Second, and probably easier way is to use the `host.Configurator`.  Note that this method requires an extra import statement of "github.com/go-siris/siris/core/host" when using go < 1.9, if you're targeting on go1.9 then you can use the `siris#Supervisor` and omit the extra host import.  All common `Runners` we saw earlier (`siris#Addr, siris#Listener, siris#Server, siris#TLS, siris#AutoTLS`) accept a variadic argument of `host.Configurator`, there are just `func(*host.Supervisor)`. Therefore the `Application` gives you the rights to modify the auto-created host supervisor through these.  Example Code:  All HTTP methods are supported, developers can also register handlers for same paths for different methods. The first parameter is the HTTP Method, second parameter is the request path of the route, third variadic parameter should contains one or more context.Handler executed by the registered order when a user requests for that specific resouce path from the server.  Example code:  In order to make things easier for the user, Siris provides functions for all HTTP Methods. The first parameter is the request path of the route, second variadic parameter should contains one or more context.Handler executed by the registered order when a user requests for that specific resouce path from the server.  Example code:  A set of routes that are being groupped by path prefix can (optionally) share the same middleware handlers and template layout. A group can have a nested group too.  `.Party` is being used to group routes, developers can declare an unlimited number of (nested) groups.  Example code:  Siris developers are able to register their own handlers for http statuses like 404 not found, 500 internal server error and so on.  Example code:  With the help of Siris's expressionist router you can build any form of API you desire, with safety.  Example code:  At the previous example, we've seen static routes, group of routes, subdomains, wildcard subdomains, a small example of parameterized path with a single known paramete and custom http errors, now it's time to see wildcard parameters and macros.  Siris, like net/http std package registers route's handlers by a Handler, the Siris' type of handler is just a func(ctx context.Context) where context comes from github.com/go-siris/siris/context. Until go 1.9 you will have to import that package too, after go 1.9 this will be not be necessary.  Siris has the easiest and the most powerful routing process you have ever meet.  At the same time, Siris has its own interpeter(yes like a programming language) for route's path syntax and their dynamic path parameters parsing and evaluation, I am calling them "macros" for shortcut. How? It calculates its needs and if not any special regexp needed then it just registers the route with the low-level path syntax, otherwise it pre-compiles the regexp and adds the necessary middleware(s).  Standard macro types for parameters:  if type is missing then parameter's type is defaulted to string, so {param} == {param:string}.  If a function not found on that type then the "string"'s types functions are being used. i.e:  Besides the fact that Siris provides the basic types and some default "macro funcs" you are able to register your own too!.  Register a named path parameter function:  at the func(argument ...) you can have any standard type, it will be validated before the server starts so don't care about performance here, the only thing it runs at serve time is the returning func(paramValue string) bool.  Example code:  A path parameter name should contain only alphabetical letters, symbols, containing '_' and numbers are NOT allowed. If route failed to be registered, the app will panic without any warnings if you didn't catch the second return value(error) on .Handle/.Get....  Last, do not confuse ctx.Values() with ctx.Params(). Path parameter's values goes to ctx.Params() and context's local storage that can be used to communicate between handlers and middleware(s) goes to ctx.Values(), path parameters and the rest of any custom values are separated for your own good.  Run  Static Files  Example code:  More examples can be found here: https://github.com/go-siris/siris/tree/master/_examples/beginner/file-server  Middleware is just a concept of ordered chain of handlers. Middleware can be registered globally, per-party, per-subdomain and per-route.  Example code:  Siris is able to wrap and convert any external, third-party Handler you used to use to your web application. Let's convert the https://github.com/rs/cors net/http external middleware which returns a `next form` handler.  Example code:  Siris supports 5 template engines out-of-the-box, developers can still use any external golang template engine, as `context.ResponseWriter()` is an `io.Writer`.  All of these five template engines have common features with common API, like Layout, Template Funcs, Party-specific layout, partial rendering and more.  Example code:  View engine supports bundled(https://github.com/jteeuwen/go-bindata) template files too. go-bindata gives you two functions, asset and assetNames, these can be set to each of the template engines using the `.Binary` func.  Example code:  A real example can be found here: https://github.com/go-siris/siris/tree/master/_examples/intermediate/view/embedding-templates-into-app.  Enable auto-reloading of templates on each request. Useful while developers are in dev mode as they no neeed to restart their app on every template edit.  Example code:  Each one of these template engines has different options located here: https://github.com/go-siris/siris/tree/master/view .  This example will show how to store and access data from a session.  You don’t need any third-party library, but If you want you can use any session manager compatible or not.  In this example we will only allow authenticated users to view our secret message on the /secret page. To get access to it, the will first have to visit /login to get a valid session cookie, which logs him in. Additionally he can visit /logout to revoke his access to our secret message.  Example code:  Running the example:  But you should have a basic idea of the framework by now, we just scratched the surface. If you enjoy what you just saw and want to learn more, please follow the below links:  Examples:  Built'n Middleware:  Community Middleware:  Home Page:
Keywords: cross-platform|crossplatform|easy-to-use|framework|go|golang|high-performance|http2|http2-server|https|iris|party-middleware|quic|quic-server|siris|tls|web-framework