thevar1able/ClickHouse
1
0
Fork 0
mirror of https://github.com/ClickHouse/ClickHouse.git synced 2024-11-18 21:51:57 +00:00
Code Issues Packages Projects Releases Wiki Activity
871cce61fa
ClickHouse/base/poco
History
Alexander Sapin a74bc6190d Implement suggestion
2023-07-03 15:46:30 +02:00
..
Crypto Remove some code 2023-04-23 06:50:42 +02:00
Data Remove some stuff from poco 2023-04-23 14:48:45 +00:00
Foundation Remove MemoryPool from Poco because it's useless 2023-07-03 14:38:38 +02:00
JSON Poco: POCO_HAVE_INT64 is always defined 2023-02-22 13:48:29 +00:00
MongoDB Update MongoDB protocol 2023-05-22 09:05:23 +00:00
Net Implement suggestion 2023-07-03 15:46:30 +02:00
NetSSL_OpenSSL Remove ConsoleCertificateHandler 2023-06-26 04:27:50 +02:00
Redis Remove Windows 2023-02-14 22:13:11 +00:00
Util Remove some stuff from poco 2023-04-23 14:48:45 +00:00
XML Remove Windows 2023-02-14 22:13:11 +00:00
CMakeLists.txt More fine-granular warning relaxation 2023-02-08 11:21:59 +00:00
LICENSE Move poco to base/poco/ (#46075) 2023-02-08 12:04:11 +01:00
README.md Move poco to base/poco/ (#46075) 2023-02-08 12:04:11 +01:00

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.