qasync's profile picture. QAsync is a new way to write asynchronous Qt applications. Single thread, multiple simultaneous asynchronous tasks.

QAsync

@qasync

QAsync is a new way to write asynchronous Qt applications. Single thread, multiple simultaneous asynchronous tasks.

Just make sure that everybody has found it... The source code is available here: gitorious.org/~hhedberg/qt/q…


Our white paper explains the motivation behind the solution and the actual implementation: qasync.henrikhedberg.com/whitepaper


QAsync is a new way to write asynchronous Qt applications: qasync.henrikhedberg.com


The source code is actually pushed out already. Who is the first to find it?


Our web page will be up and live on Wednesday!


We took one week off, but we are almost ready to share our solution with you now. It will happen within few days!


All asynchronous functions end up calling QAsync::waitAsync(), which gives control back to the Qt's event loop until the task has completed.


In the core of our solution is a new class: QAsync. It provides means to suspend a function until an asynchronous task has completed.


@kypeli It is an alternative way to express functionality. With QAsync, there no need to split asynchronous code into separate slots.


What is QAsync? It is a new way to write asynchronous Qt applications. Single thread with multiple simultaneous asynchronous tasks.


This week we will go deeper into internals of our solution. We will also focus on finalizing the release, so there will be less tweeting.


The catch in our Node example is closure. The execution context may be easily shared between "slots" when practical. pastebin.com/jFh8Ea9G


We like to learn and get inspired from other languages and frameworks. Now the TCP server is implemented using Node. pastebin.com/jFh8Ea9G


QAsync 님이 재게시함

@qasync Is the solution to generate some code at compile-time (like moc does) or is there run-time tricks (or both)?


Actually, our solution is based on signals and slots. We will introduce an alternative way how those can be used. #Qt


Do we hate signals? No, absolute not! We love signals, the best thing since sliced bread. We just think that choices are needed sometimes.


Here is another working example. This time it is a client-side utility function to fetch data addressed by an URL. pastebin.com/ULXhk1fL


QAsync 님이 재게시함

@qasync I think that you should open this solution to community :) will it be part of qt5?


Finally! Here is the working version of the original #Qt code. Just a word with five letters added. What do you think? pastebin.com/1WqE7321


QAsync 님이 재게시함

@qasync we are all waiting for your async solution :) where is it?


United States 트렌드

Loading...

Something went wrong.


Something went wrong.