Cutelyst 0.9.0 is out!
Cutelyst the Qt Web framework just got a new release!
I was planning to do this one after Qt 5.5 was out due to the new qCInfo() logger and Q_GADGET introspection, but I'll save that for 0.10.0.
This release brings some important API breaks so if everything goes well I can do another CMlyst release.
- Some small performance improvements with QStringRef usage and pre-cached _DISPATCH actions
- Fixes when using uWSGI in threaded mode
- Speedup uWSGI threaded mode, still slower than pre-forked but quite close
- Fixes for the session handling as well as having static methods to make the code cleaner
- Fix uWSGI --lazy-apps mode
- Use PBKDF2 on Authentication plugin
- Requite CMake 3.0 and it's policy
- Add Request::mangleParams() and Request::uriWith() so that Request API now covers all of Catalyst's
- Documented some functions
Cutelyst repository was moved to gitlab and then moved to github. The main website http://cutelyst.org is now powered by CMlyst and itself :)
Download here.
I also started another project, html-qt is a library to create a DOM representation of HTML following the WHATWG specifications, it's needed for CMlyst to be able to remove XSS of published posts, at the moment it has 90% of the tokenizer ready, and 5% of the parser/tree construction code, so if you have interest in the subject (could be potentially useful for mail clients such as KMail) give me a hand!
Cutelyst 0.8.0 - featuring better stats
Cutelyst the Qt Web Framework just got a new release!
With 0.8.0 some important bugs got fixed which will allow for the CMS/Blogger app CMlyst to get a new release soon. Besides bugs being fixed a class to take out stats from the application was created, Cutelyst::Stats matches what Catalyst::Stats does, and produces a similar output:
- There you have a box, and the time which each action took to complete, looking at the /End action it is clear that it took more time but most of the time was due it calling the Grantlee View.
- On the Request took: ... line there is the 1278.772/s value which means how many requests could be handled within a second, of course that value is for the exact same request and for the single core where it was run.
- The first line now shows which HTTP method was used, which resource the user wants and where the request came from.
All of that can and should be disabled on production by setting cutelyst.*.debug=false on the [Rules] section of the application ini file (--ini of uWSGI). Yeah this is new too :)
Speaking of debugging we now have more information about what user data was sent, if cutelyst.request.debug logging category is enabled you will see:
A similar output is printed for url query parameters and file uploads.
The HTTP/1.1 support for chunked responses was added, once c->response()->write(...) is called the response headers are send and a chunk is sent to the client, this is new and experimental, but worked without complaints from web browsers.
An easier way to declare action arguments or capture arguments was implemented, :AutoArgs and :AutoCaptureArgs, both are not present in Perl Catalyst because there is no way to introspect methods signature in the language, @_ can provide many things, but with Qt meta information we can see which types of arguments a method has as well as how many arguments:
C_ATTR(some_method, :Local :AutoArgs) void some_method(Context *c, const QString &year, const QString &month);
That will automatically capture two arguments matching an URL like "/some_method/2014/12".
Last the Headers class got many fixes and improvements such as striping the fragment due RFC 2616.
As always if you have questions show up in #cutelyst at freenode or send me a mail.
Download 0.8.0 here
Enjoy!
Cutelyst 0.7.0 is out and now has a tutorial!
Cutelyst the Qt/C++ web framework just got a new release, 0.7.0 brings many improvements, bugfixes and features.
Most notably of the changes is a shinny new Chained dispatcher that finally got implemented, with it Cutelyst Tutorial got finished, and a new command line tool to bootstrap new projects.
- Request::bodyData() can return a QJsonDocument is content-type is application/json
- Chained dispatcher
- Fixes on QStringListeral and QLatin1String usage
- More debug information
- Some API changes to match Catalyst's
- Some rework on the API handlying Plugins (not the best thing yet)
- Moved to Gitlab (due to the gitorious being acquired by it)
- "cutelyst" command line tool
For the next release I'll try to make the QML integration a reality, and try to improve the Plugins API, which is right now the part that needs more love would love to hear some advice.
Download it here.
Have fun!
Cutelyst 0.6.0 is released
Cutelyst, the Qt/C++ web framework just got another step into API stabilization.
Since 0.3.0 I’ve been trying to take the most request per second out of it, and because of that I decided to replace most QStrings with QByteArrays, the allocation call is indeed simpler in QByteArray but since most of Qt use QString for strings it started to create a problem rather than solving one. Grantlee didn’t play nice with QByteArray breaking ifequal and in the end some implicit conversions from UTF-8 were triggered.
So on 0.6.0 I’ve replaced all QByteArray usage in favor of QString, and from the benchmarks of hello world the difference is really negligible.
Another big change I actually took today was to change the Headers class that is used on Request and Response, the keys stored there were always in camel-case style and split by dashes, and if you want to get say the User-Agent in a Grantlee template it won’t work as dashes will break the variable name, so now all keys are lower casa and words are separated by underscores. Allowing for {{ ctx.request.headers.user_agent }} in Grantlee templates.
Some changes were also made to make it behave more close to what Catalyst does, and fixed a bunch of bugs from last release.
On my TODO list still need to:
Write a chained dispatcher to allow a more flexible way of dispatching.
Write tutorials, yeah this is boring…
Write QML integration to allow for writing the application logic in QML too!
This last one would allow for something like this:
Application {
Controller {
Action {
attributes: ":Path(hello)"
onRequest: {
ctx.response.body = "Hello World!"
}
}
}
}
Download here
Have fun!
Cutelyst 0.4.0 is out!
This is yet another big step for Cutelyst, this release bring several important fixes to the last version, and stabilizes the API a bit more. So far I have successfully deployed 3 commercial applications build on top of Cutelyst + Grantlee5, and the result is great. If you don't know Cutelyst yet it's a Web Framework allowing you to build web applications using Qt, for more info check (this blog and) our website/wiki which is still work in progress: http://cutelyst.org or join #cutelyst on freenode This release brings the following improvements:
- Further speed improvements by simplifying several code paths and improving the dispatcher logic was an overall of 15% speedup
- Added an API to enable Grantlee template caching which greatly improve speed when using Grantlee templating
- Improved Query and Body parameters to allow for properly dealing with posts that contains the same field id multiple times
New features:
- REST API - Since 0.1.0 I was asked about supporting REST, and since I needed it for another project that I got involved the support landed early, the behavior is the same as Catalyst::Action::REST which allows you to easily add a foo_DELETE method which will get automatically called if the request method is DELETE for example.
- Added a Credential HTTP plugin to handle Basic HTTP (and in future Digest) authentication
- Added support for Authenticate and ProxyAuthenticate basic parsing on the Headers class
- Finished Context::uriFor() methods that allows for easily building an URI.
- Added a method to do a DNS PTR lookup to get the hostname of the client
- Added a C_PATH to more easily set the matching part of the path (thanks to Dan Vrátil)
Fixes:
- Fixed a few memory leaks
- Fixed a crash if the body wasn't set
- Fixed uWSGI body buffered device
- And a lot of other misbehaviors found on post release...
For the next release I hope to be able to port the Catalyst tutorial to the Cutelyst equivalent, and finish a few other API changes. As before the API is unstable but don't be afraid of playing with it, most changes will simply require a rebuild of your application.
Have fun!
https://gitorious.org/cutelyst/cutelyst/archive/0f28d7da9b04061fe80f7e9cf24a120250a02e02.tar.gz