Future

The focus of this bistro release was establishing a baseline implementation of language and patterns in bistro. There are still some key aspects missing, that will be added over the course of the next few iterations.

• Usability
  • Extend the attribute list
    • Support for a "body" attribute, etc.
    • Support for declarative input sanitation
  • Introduce a standard formatter/serializer nomenclature, for allowing inbound values to be transformed declaratively (e.g. if an inbound form field carries a JSON structure, use something along the lines of [FormField(ContentType.JSON)] on a complex type) (implemented in 0.9.1.0)
  • Use the same formatter approach to expand the ReturnXXX methods to take object graphs, rather than pre-serialized fragments (implemented in 0.9.1.0)
  • Review the Bind syntax. Over the course of our development, a number of requests came up for extended bind syntax. These requests need to be reviewed, and potentially incorporated.
  • Declarative validation (implemented in 0.9.1.0)
  • Declarative entity mapping (implemented in 0.9.1.0)
• Performance
  • Improved dispatcher implementation. The current dispatcher implementation does well, but there is always room for improvement
  • Controller chain precomputation. The controller bind syntax defines a complete graph of all possible serviceable requests. Currently, each chain is computed on demand. Precomputing this chain will speed performance
  • Controller chain precompilation. Building on controller chain precomputation, we can precompile each pathway of a controller chain, and significantly reduce the use of reflection during controller invocation

... and much more.

The focus is, and will always be, however, on backwards compatibility. We will make sure that all new features allow previous implementations to remain unaffected.