The POCO C++ Libraries Blog

POCO 1.3.4 Available

Filed under: News by guenter at 17:12

I am happy to announce that release 1.3.4 is finally out! Apart from the usual bugfixes, this release contains significant performance improvements as well as some nice new features, such as a writable XMLConfiguration, a refactored NetSSL_OpenSSL library, support for case-insensitive globs, a new Poco::Util::Timer class, new PriorityNotificationQueue and TimedNotificationQueue classes in Foundation, and much more. See the CHANGELOG for a complete list of changes.

Thanks to everyone who contributed to this release. And thanks for your patience waiting so long for it.

  1. Poco on GitHub?

    Comment by Raj on April 21, 2009, 19:09

  2. I’ve been intrigued by Git since I saw the Torvalds’ Google speech. I wish day had 48 hours, though. It takes time to evaluate it and make a decision for a move like that.

    Thanks for your hard work, Guenter.

    Comment by alex on April 21, 2009, 22:02

  3. Great news! Thank you for pushing hard for this new release!

    Comment by Viet on April 22, 2009, 02:28

  4. Awesome!

    Don’t know if you guys use/test it under QNX6 but it’s working for me!

    Comment by Mario on April 23, 2009, 19:47

  5. Regarding GitHub: this would be an option, given enough resources to do the switchover. Primary blocking point at this time would be the time needed to familiarize with Git.

    Regarding QNX: I do run a build and a testsuite run on QNX (x86 under VMware) as part of release testing. We have a few failing testcases on QNX (in the Net library) – we should really document these here on the website (also for other platforms).

    Comment by guenter on April 23, 2009, 20:12

  6. Hello:
    I am new here. I got to compile/link under WinXP SP3 using VS2008Pro without problems thanks to indications given into the README.
    Let me ask a first question here, which (temporal?) objects generated by VS2008 should I consider to delete? The reason is that the folder that contained POCO, including documentation, initially had 25MB and it grew up to 861MB after executables generation.
    Thank you for the attention and congratulations for your nice work.
    Best regards.

    Comment by Vizcayno on April 24, 2009, 18:47

  7. After building, you can safely delete all directories named “obj” in Foundation, XML, Util, Net, etc. These contain object files and other temporary files created during compilation.

    Comment by guenter on April 24, 2009, 20:01

  8. Hi Vizcayno,

    I wrote ExtCleaner for myself some time ago using Poco library. It cleans files with specified extensions recursively inside specified directory. The code itself very simple. You can download from the URL below:

    Comment by Viet on April 27, 2009, 16:56

  9. You may get it from here:

    Comment by Viet on April 27, 2009, 17:20

  10. Amazing framework. Are there plans for OAuth?

    Comment by Nathan on April 30, 2009, 04:37

  11. Viet:
    Many thanks for your interest. I read and compiled the program you kindly indicated. During execution I have got next error: The procedure entry point ??1AtomicCounter@Poco@@QAE@XZ could not be located in the dynamic link library PocoFoundationd.dll (also happens with PocoFoundation.dll).
    I had previously removed obj files. Meanwhile and checking your code, I manually deleted the remaining files: .pdb, pch, idb, ilk, as a result the size of “poco” was reduced to 93MB.
    Very best regards.

    Comment by Vizcayno on May 1, 2009, 14:43

  12. Hi Vizcayno,

    Thank you for correspondence. I have not faced that issue in both Windows and Mac OS X. The error is very strange and I have no clue about it…

    You can drop me an email to with details and to avoid cluttering Poco Blog 🙂 I hope Poco developers won’t be too strict on these 2 comments.


    Comment by Viet on May 2, 2009, 05:18

  13. “The procedure entry point ??1AtomicCounter@Poco@@QAE@XZ could not be located in the dynamic link library PocoFoundationd.dll.”

    You have an old DLL loaded at runtime. AtomicCounter has been introduced in 1.3.4. Dependency Walker utility is very helpful in determining what gets loaded at runtime.

    Comment by alex on May 3, 2009, 13:25

  14. Thank you Alex! I was using 1.3.3p1 to develop the ExtCleaner and was not aware of the AtomicCounter since it was introduced in 1.3.4. Now Vizcayno will know that he needs to update DLLs accordingly or just go back to 1.3.3p1.

    Comment by Viet on May 5, 2009, 03:38

RSS RSS feed for comments on this post. TrackBack URI

Leave a comment