Track

Difference between version 9 and 11 - Previous - Next
A work in progress https://github.com/mpcjanssen/track%|%library%|% for making a small web framework. Heavily inspired by the Elixir Phoenix framework request pipelining and routing

The name is a pun on Rails and starts with a T so we have Tcl on Track.

**Design**

   * Functional: most functions will transform a dict containing the information about the request and response.
   * Composable: it should be possible to combine request dict transformers in arbitrary order. This makes it possible to pick and choose parts of the "framework" and make it easy to extend. 
   * Prefix based: All defined callbacks are treated as prefixes.
   * Re-usable: The transformers should be usable with any dict of the right structure. For example, the router could be useful in other contexts than web servers and should be usable in that way.
   * Explicit: there should be no magic. The flow of application should be easy to follow. An example is the routing table specifying the exact proc that is called. And handlers needing to extract the request params instead of upvar or similar gymnastics.
    * Standard: basic Tcl structures and idioms should be used as much as possible. So for example the routes definition is a simple Tcl list which can be dynamically built and modified using standard Tcl.


**Components**


****Server****

Libraries of server connectors to convert the incoming request to a dict with the required parts correctly filled. For example socket should contain the client socket and path the query path.

Available:

   * SCGI



****Router****

The router library takes a request dict and takes the path element an a routes list. It will then determine which route matches and call the associated prefix command with the request dict as last parameter (or without if the prefix start with !)

While matching the route, parts which start with @ or : will match anything and the matched part will be stored in the req dict as params. The difference between @ and : is that @ will also match any following slashes.

Example:

======
set routes {    /rest/:id                    rest::handler
    /rest/:id/:subresource       rest::handler
    /flavor/a/:code            {flavor::handler a}
    /flavor/b/:code            {flavor::handler b}    /css/default.css            {track::asset default.css text/css}
    /                           {track::md index.md}
    /console                        {!console show}
    /exit                        {!exit}
    @rest                       track::debug_req
}
======

****Track****

Library of transformer functions which take a dict and perform useful transformations and side effects. For example mirroring an additional http request to the client.

Also contains helper functions to extract parts of the request dict without assuming the structure. For example `[@p $req name]` to get the name parameter from the request.