thevar1able/ClickHouse
1
0
Fork 0
mirror of https://github.com/ClickHouse/ClickHouse.git synced 2024-11-12 18:45:20 +00:00
Code Issues Packages Projects Releases Wiki Activity
937ce8f780
ClickHouse/base/poco
History
Sema Checherinda fb2f0e78f7
Merge pull request #63985 from ianton-ru/protocols-tls-extend-params 
More parameters for tls layer in protocols
2024-06-24 12:41:56 +00:00
..
Crypto Revert "Suppress false positives in leaksan" 2024-06-19 08:30:44 +00:00
Data Merge branch 'master' into fix-comment 2023-08-10 17:03:31 +03:00
Foundation Initialize global trace collector for Poco::ThreadPool 2024-06-13 19:20:58 +02:00
JSON Fix build with clang-19 (master) 2024-04-03 05:42:41 +02:00
MongoDB Fix MongoDB connection issues 2023-10-09 14:46:48 +00:00
Net Revert "Use 1MB HTTP buffers to avoid frequent send syscalls" 2024-06-20 17:06:18 +02:00
NetSSL_OpenSSL Merge branch 'master' into protocols-tls-extend-params 2024-06-20 19:02:12 +02:00
Redis
Util Correctly handle keys with dot in the name in configurations XMLs 2023-12-29 17:30:23 +01:00
XML
CMakeLists.txt
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.