The POCO C++ Libraries Blog

POCO is on the Move

Filed under: News by alex at 03:15

After many months of absence and low-level involvement with the project (for personal and professional reasons), I am back. We also have commitment from two other community members (Marian Krivos and Franky Braem) to help significantly with the project. For starters, Marian has retired old and I have just committed brand new trunk code. For the time being, it was only built on Windows, but we’ll have other builds ready within the next week or two.

Most significant new features are:

  • DynamicAny (now known as Poco::Dynamic::Var, although Poco::DynamicAny will still work) improvements
  • Poco::Data improvements (DateTime support, bulk operations, SessionPool, Transaction support, async SQL execution, in-memory SQLite … warning, though – we broke old Poco::Data code!)
  • Poco::PDF library
  • Poco::JSON library and Poco::Util::JSONConfiguration (not in the trunk yet, will be soon)
  • VS project generator
  • PocoDoc generator

And many more other improvements. This code is base for 1.5 release, which we are targeting for mid-SeptemberĀ Aug 27 July 4 30 (to steal the fireworks thunder šŸ˜‰ ). At the same time, we are actively working with C++ Standards Committee on the proposal for inclusion of POCO into the C++ standard. Yes, async I/O is on our TODO list. I won’t promise it for 1.5, though, unless I get a committed contributorĀ willingĀ to write it.

Which brings me to the “last but not least”: we need contributors (library or build/test system owners/maintainers in particular) and sponsors. If you areĀ benefitingĀ from POCO, please consider helping in any way you can. This can be by contributing code, owning a library or other concern (build system, tests, samples, platform, OS installation packages …), providing CI server space, sponsoring, etc.

Let’s join forces and give POCO the boost (no pun intended) it deserves.

EDIT (Oct 15 2012): little bit more than 3 months late, we have POCO 1.5.0. Thanks to everyone who helped with this release.

  1. excitingļ¼
    I wonder if ver1.5 will base C++11 more than beforeļ¼Ÿdue to current major compilers already support most of the useful features.
    One possible improvement of UnicodeConverter is using u16string instead of wstring which stands for utf-16 only on windows.
    Async I/o reference I suggest two candidates: push framework and libuv

    Comment by pillaridge on April 23, 2012, 17:49

  2. There will be some C++11 support in 1.5 (move semantics and lambdas). Full support is planned for 2.0. Looking forward to drop some of the old baggage.

    Cross-platform asynchronous I/O is a mess. Most likely we’ll do it from the scratch. At this time, we’re waiting to see where C++ Standards Committee stands on the topic.

    Comment by alex on April 23, 2012, 22:26

  3. Hi Alex and the POCO team! That’s great news! By the way, why don’t you create gift token where developers can register for small recurring contributions like $20/month? :) Sponsors mostly meant for companies, but there are lots lots of enthusiasts out there, like me.

    Comment by Viet on April 24, 2012, 02:44

  4. Looking for someone to test/maintain the QNX version?

    Comment by Mario on April 25, 2012, 17:03

  5. yes. email me at(alex, dot(pocoproject, org))

    Comment by alex on April 26, 2012, 12:58

  6. Any update when 1.5 will be released

    Comment by jrb on August 30, 2012, 18:49

  7. I know, I know … I screwed up by committing to dates and then kicking them down the road. Most of the things are done, we’ll do our best to push it out in September. I’ll update the blog post.

    Comment by alex on August 31, 2012, 00:53

  8. Hi, it’s Oct now. Any update about 1.5? :)

    Comment by clsung on October 5, 2012, 09:41

  9. Yeah, almost there. Sometime next week …

    Comment by alex on October 6, 2012, 09:15

  10. Thank you very much, I love this project. Hope I can contribute codes back soon.

    Comment by clsung on October 7, 2012, 12:31

RSS RSS feed for comments on this post. TrackBack URI

Leave a comment