io_service is awesome but there's a couple of things that have to happen to make it work. First, io_service only works if you tell it to work, by either calling the member functions run(), poll(), run_one(), or poll_one(). That's the first part. Note: the run() function will block until it doesn't have any more work, which is important for the next part. Most applications want to start io_service before there's any work to do, but if you did this...

1. io_service.run();
2. GAPost gaPost( io_service ); 

...the io_service would've finished before calling GAPost and so every async call you make will not be completed. What you'd most likely want to do is create "work" for it before running it.

1. asio::io_service::work work( io_service );

This will keep the io_service working until you call work.stop(). The next thing is the difference between the activation functions on io_service. If you make the wait call, then the io_service.run() call above. You'll never reach the GAPost constructor line. Like I notated above run will block the thread until there's no work to do, and you'll never be able to call work.stop(). Poll won't block. It will run whatever functions have been posted to the queue and then return. That's what you'll want unless you "run" io_service on a seperate thread. Let me know if any of that doesn't make sense and if I didn't answer your question at all. :)

https://github.com/cinder/Cinder/blob/master/src/cinder/app/AppBase.cpp

1. ci::app::App::get()->io_service()

Thanks!

Is there something I should be calling on app exit to release/clean/un-bind the io_service?