C++ Standard Library Size*

I presented Poco::Net to the SG4 and we discussed the proposals for the standard networking library. There were two other proposals presented/reviewed: asio as the networking/IO library and URI proposal from cpp-netlib. The consensus was that solid networking foundations should be built first – C++ standard needs networking types on which the standard network library can be built.

The result of the discussion was a tentative wish-list/agenda for proposals/implementations:

2012 – URI and IPv4/6 Address

2013 – HTTP and Resolvers (DNS, maybe more)

By this time, we’d hope to have fully defined async model (waiting on the SG1 discussion outcome). Something that is still uncertain to some extent is what exactly does std::async(std::launch::async) do – is it obligatory to  to launch an OS thread in the background or is the async behavior just “as if” the OS thread was launched, leaving room for other asynchronous back-end modes of operation.

2014 – sockets, async socket streams

2015 – ICMP, SSL

As things currently stand, we will be proposing portions of POCO for standardization. Günter and I will be working on a formal proposal for URI and IP Address, aiming to have it ready before the October meeting in Portland, OR. We will also soon start working on the Poco::Net based standard socket library proposal.

Also, before Portland meeting, we will comb through Foundation, start weeding out code addressed by C++11 and extract a subset that would make sense to be proposed for the next round of standardization. What exactly? Dynamic typing, caching, (de)compression, processes, various streams etc etc. This list does not even get into configuration, application, options, XML, JSON, database, … all of which are called for and sorely needed.

Our involvement in the standardization came from Herb Sutter’s call to C++ community (if impatient, scroll to 1:15 mark or just look at the picture below to get the idea) to get together and put forth an effort to create a standard C++ library comparable in size and utility to the one Java and C# have.

Portable C++ Library*

As you can see from the above, the list is long, while time/manpower is short. A well-designed, standard-compliant and highly-portable framework community like POCO has a lot to offer to the C++ effort. As usual – I am asking for help. Participating in standardization process can be a rewarding experience, so if you have any inclination or desire to be part of the process, by all means let us know. More baggage we can drop-off to the standard implementation, more time and better foundation we’ll have to build new features on.

Do you want to help/participate in POCO proposals for C++ Standard? Let us know:

at(alex, dot(pocoproject, org));

Thanks to all who have contributed so far and will do so in the future!

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 July 4 (to steel 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.

Günter

For more information about our new my-devices.net platform providing secure remote access to the built-in web server of smart devices, please visit my-devices.net.
For more information about the CODE_n 12 contest, please see here.

Looking forward to see you at CeBIT hall 16 in March.

Merry Christmas