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
- 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)
- 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.
Release early, release often has never been my strength especially since I don't do a fair scheduling of all the projects I'm involved...
So since I was in need to better polish Cutelyst I took more time on it, and the result is great, around 100% speed up and a few new features added.
Cutelyst uWSGI plugin now has support for --thread, which will create a QThread to process a request, however I strongly discourage its usage in Cutelyst, the performance is ~7% inferior and a crash in your code will break other requests, and as of now ASYNC mode is not supported in threaded mode due to a limitation in uWSGI request queue.
Thanks to valgrind I managed to make a hello world application from 5K request per second on 0.2.0 to 10K req/s on 0.3.0 on an Intel Core2Duo 2.4Ghz (or 44K req/s on an AMD Phenom II 965 x4 3.4Ghz), however if you enable Grantlee templating you get around 600 req/s so if I happen to have time I will be looking into improving its performance.
Response::body() is now a QIODevice so you can set a QFile* of something else and have Cutelyst to send it back.
Now http://cutelyst.org points to a gitorious Wiki which is slowly getting populated, and API is available as http://api.cutelyst.org.
The 0.3.0 tarball can be downloaded here
Have fun :)
Five months ago I announced the very first release of Cutelyst, a web framework powered by Qt 5. Time passes and I started shaping my real world applications written with it, I should probably release a newer version earlier but it's not very nice to keep releasing API that changes a lot, however next version (0.3.0) will still contains API changes. What changed from 0.1.0 to 0.2.0:
- I have setup a documentation website http://cutelyst.org
- I started a WordPress like blog written with Cutelyst https://gitorious.org/cutelyst/untitled this right now is a nice example app, if you like it please help :)
- Changed the API to expose the forked behavior thus being able to setup database connection in each new process avoiding a mess
- UWSGI got a patch to deal with workers that don't want to work, in other words when something on post-fork fails like reaching the dababase connection limit the worker can exit and won't be restarted.
- A bunch of bugfixed of course
- Make use of categorized logging (ie qCDebug)
- Allow for UWSGI to restart the application as soon as your application .so file changes, this greatly improve development speed :)
- Encapsulated the post body into a QIODevice subclass on UWSGI engine this means a QFile is --post-buffering limit is reached, or a custom IODevice that deals with the request memory buffer
- A parser to get uploaded content "multipart/form-data" which is fast and can work with lots of data
For the next version I'll try to get a properQt loop integration.
Three months ago Custelyst was started, it was somehow a proof of concept to see if I could build something that could be used in the real world, but the more I progressed on getting all the pieces together the happier with the overall result I got. And the initial result is here today! I have made a few benchmarks comparing some simple pages delivery using Django (python) and Perl Catalyst, and overall the time to first byte was around 3 times faster than both, comparing RAM usage it was like 2MB vs 50MB from the Perl version and 20MB of the Python one, the CPU time was also much smaller if compared to both which probably means it could handle more requests, but this isn't a completely fair benchmark (as always) because there are several other things to measure... Below I'll try to clarify some doubts raised from my last post and what makes this new Web Framework unique:
But there is already QDjango and Tufao...
I didn't know about these ones when I first started Cutelyst, but after taking a look at them, both misses a templating system (or integration with one), I also didn't like the way one would register actions to be dispatched, IMO the way it's done in Cutelyst is easier and nicer. And they doesn't count with WSGI integration, they have their own HTTP parser/server. I also didn't like looking at code :P
Why not DJango or any other well established framework out there?....
Apart from QDjango and Tufao there are no other (AFAIK) Qt based frameworks, there are indeed some C++ ones that I knew before but I didn't like the way of doing things there, in fact when I started with Perl Catalyst I really liked how it was written. So in short I don't know well enough other languages and I have no plans wasting my time learning other languages, I'd rather try to master at least one (although I know I'm far from it).
What's in this release?
- Glad you asked (duh!)
- Production ready integration with uWSGI, meaning Cutelyst has a uWSGI plugin that will load your application (which will also be a plugin), and thus thanks to uWSGI it will have out of the box support for FastCGI, HTTP(s), uWSGI (protocol) and probably some other.
- ClearSilver templates integration, this templating system is written in C and it's amazingly fast, but it's also incredible limited to what you can do in the view.
- Grantlee (Django) templates integration, it's used in KDE PIM to allow for easy templating of HTML, it's slower than ClearSilver but offers much more fexibilities on your views, and since it's also written in Qt the introspection comes for free.
- Complete Path dispatcher, which means if you Port a Perl Catalyst Application that was using Path actions it will work as expected. This dispatcher matches an url to a Q_INVOKABLE method depending on it's signature, The Catalyst Chained dispatcher is not implemented yet.
- Session plugin, easy to use way of persisting data across requests, right now it's done with a QSettings file, but integration with Redis and MongoDB are planned.
- Authentication plugin, allowing you to authenticate your users using different Realms/stores, currently a StoreMinimal is implemented which can be used mostly for testing purposes (ie on the code you add your users)
- StaticSimple plugin, allows for serving static content reducing the complexity of serving static content while developing your app.
If you are concerned about API/ABI stability I don't promise it just right now it's almost stable, probably 0.2 or 0.3 versions will have a promised stable API. And yes, I have just put it on production http://serial.igloobox.com.br is running it right now (but the site is user restricted). My plans now is to setup cutelyst.org with docs and examples, as well as writing a web blog, bug tracker and wiki based on it.
Do you recall that "Qt everywhere" branding?
Well that's one of the things I really like in Qt, being able to deploy everywhere with minimal to zero changes in source code. But sometimes your application needs a web interface some sort of web backend or web admin, and when that happens it breaks that slogan (AFAIK)...
I got in contact with web languages (not HTML) only when at university, ColdFusion and PHP where the first ones, and while PHP was sort of cool because it has a syntax close to C, I never really like it. I'm not a web designer nor know how to do pretty websites, but in today's world building web apps is inevitable.
So years ago I learned about RubyOnRails, and people where talking all the good stuff about it, it's was the framework of the hype, although I knew Ruby wasn't the fastest scripted language my need didn't demand that, so I got a book, read it cover to cover and happily started my web app, a week latter I got a complex problem with an apparently impossible solution. It seemed that RoR makes easy things stupidly easy and complex things impossible...
The I met Catalyst a Perl framework, got exited again, but I knew nothing about Perl so I read more 3 books and was started to love the language, I still do, but last weekend when trying to resurrect and old Catalyst application I got an error which I had no idea how to fix, on IRC I was told the problem could be that I mixed CPAN packages with distro packages, not very convinced I realized the bigger problem I was actually facing, I'm not fluent in Perl, well no matter how many books you read about a language you only get fluency in it after speaking it almost everyday, this applies to computing languages too of course.
So if 99% of the time (or less now with QML) I'm programming C++ it means that I know a lot more about how to debug it than with Perl, so Cutelyst! Writting web apps in Qt/C++ will be much more efficient to me and hopefully to you too.
I share lots of the Catalyst API and design ideas, tho the implementation is of course completely different. Also for the sake of HTML templating I plan to create a Grantlee View plugin.
You can take a look at the proof of concept: