vane 0.6.2+1

Vane is a class based server side framework.

0.6.2

• Changed behavior of logging by printing logging of proxied request to a different log level, since it can be seen in the output of pub serve anyways. It can be seen in the server output if the default logging level is changed like this:

void main() {
  serve(logLevel: Level.FINE);
}

0.6.1

• Fix MongoDB related issue #5, before we assumed there always was a MONGODB_URI enviroment variable, not optimal. Now we instead give the user three options; if no enviroment variable is set, and no paramter is provided to serve(), then we use the standard mongodb://localhost:27017 uri. If there is an enviroment variable we will use that one, if the user want a different uri it is now also possible to override the default uri with a named optional paramter to serve().

Example using default mongodb://localhost:27017 uri: void main() => serve();

Example overriding with named paramter: void main() => serve(mongoUri: "mongodb://127.0.0.1:37017");

0.6.0

• New proxy functionality to integrate Vane with pub serve for client requests. With Vane 0.6.0 cross origin requests are no longer needed.

To use the proxy you need to seperate your client and server code in a "client" and a "server" directory and have a simple app.yaml file in the app root dir. Start by running "pub serve" in your client project's directory, let it use the standard 8080 port. Then start your Vane server seperatly from the Dart Editor by right clicking "server.dart" and pressing "Run". Last but not least, go to http://127.0.0.1:9090/ and you can use Vane and pub serve together!

To easily try out Vane 0.6.0, follow these instruction:

• git clone https://github.com/DartVoid/Vane-Hello
• Open "Vane-Hello" in the Dart Editor
• Wait for the Editor to run pub get (if it don't, run it yourself)
• Right click server/server.dart and press "Run"
• Right click client/index.html and press "Run in Dartium"
• First try http://127.0.0.1:8080 , just to see that it is only the client-side that works
• Now try http://127.0.0.1:9090 instead and see that both server-side and client-side will work!

0.5.2

• Typo fixes by Victor Berchet
• Fixed github issue #6
• Added better logging, now possible to see when how Vane parses handlers and how it matches the correct handler.

See parsing of handlers (only on startup)

void main() {
  serve(logLevel: Level.FINE);
}

See parsing of handlers (only on startup) and matching of requests (on each request)

void main() {
  serve(logLevel: Level.FINER);
}

0.5.1

• Added statusCode setter

0.5.0+2

• Updated text and fixed errors in README
• Added usage examples for Tube
• Updated examples

0.5.0

• New Vane server implementation that can serve three types of handlers based on the @Route annotation. The Vane server automatically scan your dart controller/handlers and serves them based on the @Route annotation.
• New @Route annotation that can be used for Vane, Podo and Func handlers. The @Route annotation uses Url template syntax and Vane now supports mapping paramters from the Url as input paramters to handlers.
• New middleware declaration syntax:

Example of before to add one middleware that runs before the main controller and one that runs after it:

class TestClass extends Vane {
  void init() {
    pre.add(new SyncExample());
    post.add(new SyncExample());
  }
}

Example of new syntax:

class TestClass extends Vane {
  var pipeline = [SyncExample, This, SyncExample];
}

• Middleware system can now sense when a middleware runs next() and if it is last in the pipeline, it will convert the next() call to a close() call so that the request can't hang itself. A controller can also get runtime information on where in the pipeline it is and how many controllers have/will run before and after with the new paramters pFirst, pLast and pIndex.

0.3.0+2

• Updated Hello World example in README.

0.3.0

• Added support so that the user can choose a different handler function than main, main is still default but a different handler can be choosed, hence the same object can be registred on multiple different paths, now it's for example possible to map all GET request to one method and all POST request to a different one. Before you had to have two seperate classes.
• Added new shorthand for pathSegments called path. Similar to query, json, params and etc. Using pathSegments seems common enough and the default way to get it is complex enough compared to other parts of vane to be worth a shorthand.

0.2.1+1

• Moved Vane's code to a public Github repo and updated README with link to Github repo.

0.2.1

• Added some simple middleware classes. One that logs all request to the console (press "console" in dashboard of DartVoid to see it) and one that enables cross origin requests to your handler. If you enable the Cross middleware during development you can for example run the client code locally and have the server code run on DartVoid (we did this during the development of DartVoid's dashboard, it is written with Vane and has been developed on the platform it self...).

0.2.0

• Added "the tube", a new way to communicate between middleware handlers. See docs for examples.

0.1.0+1

• Syntax fix in docs.

0.1.0

• Initial release.