POCO C++ Libraries 1.3.2 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News POCO C++ Libraries 1.3.2 (Default branch)
# 1  
Old 02-04-2008
POCO C++ Libraries 1.3.2 (Default branch)

The POCO C++ Libraries are a collection of class libraries for developing network-centric, portable applications in C++. The classes integrate perfectly with the C++ Standard Library and cover functionality like threads, thread synchronization, filesystem access, streams, shared libraries and class loading, sockets and network protocols (HTTP, FTP, SMTP, etc.), including an HTTP server, as well as an XML parser with SAX2 and DOM interfaces and SQL database access. License: OSI Approved Changes:
This release brings major performance enhancements in the XML library, along with some bugfixes and feature improvements.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

1 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

POCO install throwing error

All , I am trying to install POCO lib on Solaris server. When I do make -s,I am getting the following error. make: Fatal error in reader: Makefile, line 10: Unexpected end of line seen Few of the content: # # Makefile # # The global Makefile for POCO # #sinclude config.make ... (0 Replies)
Discussion started by: prasperl
0 Replies
Login or Register to Ask a Question
hba.conf(4)															       hba.conf(4)

NAME
hba.conf - configuration file for the HBAAPI library The /etc/hba.conf file is used to specify the Vendor-Specific Libraries that are installed on the system. This file is used by the Common Library to load the individual VSLs when HBA_LoadLibrary(3HBAAPI) is called. If changes are made to the file while the library is in use, the library should be freed and reloaded. A version 1 VSL is compatible only with a version 1 Common Library. A version 2 VSL is compatible with both a version 1 and a version 2 Common Library. Each VSL entry is a single line of the form: "name" "library path" where: name is the description of library. The library name should be prepended with the domain of the manufacturer of the library. library path is the absolute path to the shared object library file. Example 1: Contents of /etc/hba.conf # # This file contains names and references to HBA libraries # # Format: # # <library name> <library pathname> # # The library name should be prepended with the domain of # the manufacturer or driver author. com.sun.fchba32 /usr/lib/libsun_fc.so.1 com.sun.fchba64 /usr/lib/sparcv9/libsun_fc.so.1 See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard: FC-MI 1.92 (API | | |version 1) | +-----------------------------+-----------------------------+ | |Standard: FC-HBA Version 4 | | |(API version 2) | +-----------------------------+-----------------------------+ HBA_LoadLibrary(3HBAAPI), libhbaapi(3LIB), attributes(5) The HBAAPI is provided in both 32- and 64-bit versions, but only one configuration file is specified. As a result, both 32- and 64-bit VSL libraries must be specified within the same file. When using the 32-bit Common Library, the 64-bit VSLs will fail to load. When using the 64-bit Common Library, the 32-bit VSLs will fail to load. These failures are silently ignored by the Common Library during normal usage, but can result in warning messages when running client applications in a debugger. 4 Sep 2003 hba.conf(4)