thevar1able/ClickHouse
1
0
Fork 0
mirror of https://github.com/ClickHouse/ClickHouse.git synced 2024-12-01 03:52:15 +00:00
Code Issues Packages Projects Releases Wiki Activity
17f27275ae
ClickHouse/base/poco
History
Robert Schulze 17f27275ae
Merge remote-tracking branch 'ClickHouse/master' into delete_old_mongodb_integration
2024-11-25 17:23:15 +00:00
..
Crypto Fix 2024-09-16 13:30:17 +02:00
Data Merge branch 'master' into fix-comment 2023-08-10 17:03:31 +03:00
Foundation Make Poco::Logger getChannel() and setChannel() thread-safe 2024-10-21 02:16:01 -07:00
JSON Fix build with clang-19 (master) 2024-04-03 05:42:41 +02:00
Net rework TCPHandler exception handling 2024-11-11 11:37:13 +01:00
NetSSL_OpenSSL Support more advanced SSL options for Keeper internal communication 2024-09-13 14:23:01 +02:00
Redis Remove Windows 2023-02-14 22:13:11 +00:00
Util Fix 'file not found' error 2024-09-03 13:28:39 +03:00
XML Remove Windows 2023-02-14 22:13:11 +00:00
CMakeLists.txt get rid of poco mongodb integration implementation 2024-11-16 00:28:54 +04:00
LICENSE
README.md

README.md

alt text

Travis Build Status Build status CII Best Practices

POCO (Portable Components) C++ Libraries are:

  • A collection of C++ class libraries, conceptually similar to the Java Class Library, the .NET Framework or Apple’s Cocoa.
  • Focused on solutions to frequently-encountered practical problems.
  • Focused on ‘internet-age’ network-centric applications.
  • Written in efficient, modern, 100% ANSI/ISO Standard C++.
  • Based on and complementing the C++ Standard Library/STL.
  • Highly portable and available on many different platforms, from embedded to server.
  • Open Source, licensed under the Boost Software License.

alt text

To start using POCO, see the Guided Tour and Getting Started documents.

POCO has an active user and contributing community, please visit our web site and blog. Answers to POCO-related questions can also be found on Stack Overflow.

Please see CONTRIBUTING for submitting contributions, bugs reports, feature requests or security issues.

In regards to Boost, in spite of some functional overlapping, POCO is best thought of as a Boost complement (rather than replacement). Side-by-side use of Boost and POCO is a very common occurrence.