Parents (Total: 72)

The searched file hash is included in 72 parent files which include package known and seen by metalookup. A sample is included below:

Key	Value
MD5	3D6C8F509FCADBE368A1AA93E0B8E5B2
PackageArch	s390x
PackageDescription	Development files for tntnet
PackageMaintainer	Fedora Project
PackageName	tntnet-devel
PackageRelease	8.fc23
PackageVersion	2.2.1
SHA-1	02A94B7BAE11FE0BAB70A9C455904740142B902A
SHA-256	51A0A7DB830A2F2B202BE1D5DF3303A4BE58B32613B45E286606942A38E95F84

Key	Value
FileSize	127992
MD5	0C3B10B952B250B65D5D2994B7179623
PackageDescription	Tntnet library development headers Tntnet has a template-language called ecpp similar to PHP, JSP or Mason, where you can embed c++ code inside a HTML page to generate active content. The ecpp files are precompiled to C++ classes called components and compiled and linked into a shared library. This process is done at compiletime. The web server Tntnet needs only the compiled component library. . Because the web applications are compiled into native code, they are very fast and compact. . Components can call other components. So you can create building blocks of HTML parts and call them in other pages like subprocesses. . Requests are parsed by tntnet and the request information is easily accessible to the components. It supports GET and POST parameters and MIME multipart requests for file upload. . The template language has also support for internationalized applications. You can easily create web applications for different languages. . Other features are: cookies, HTTP upload, automatic request parameter parsing and conversion, automatic session management, scoped variables (application, request and session), internationalisation and keep-alive. . Logging is done through cxxtools, which provides a unique API for log4cpp, log4cxx or simple logging to files or console. . Tntnet is fully multithreaded and much work has been gone into making it scalable. It uses a dynamic pool of worker threads, which answer requests from HTTP clients.
PackageMaintainer	Kari Pahula <kaol@debian.org>
PackageName	libtntnet-dev
PackageSection	libdevel
PackageVersion	2.2.1-4
SHA-1	0371E4D6F7603D85FBFBE9C0E6C0682B9E79ABB6
SHA-256	8D35CFF3A63F31522D2C8A859B908EF38D37CD8D9A8808C1A79C487FEDBB715B

Key	Value
FileSize	117946
MD5	873E6F4C208BA2978FE0120C81AE4A83
PackageDescription	Tntnet library development headers Tntnet has a template-language called ecpp similar to PHP, JSP or Mason, where you can embed c++ code inside a HTML page to generate active content. The ecpp files are precompiled to C++ classes called components and compiled and linked into a shared library. This process is done at compiletime. The web server Tntnet needs only the compiled component library. . Because the web applications are compiled into native code, they are very fast and compact. . Components can call other components. So you can create building blocks of HTML parts and call them in other pages like subprocesses. . Requests are parsed by tntnet and the request information is easily accessible to the components. It supports GET and POST parameters and MIME multipart requests for file upload. . The template language has also support for internationalized applications. You can easily create web applications for different languages. . Other features are: cookies, HTTP upload, automatic request parameter parsing and conversion, automatic session management, scoped variables (application, request and session), internationalisation and keep-alive. . Logging is done through cxxtools, which provides a unique API for log4cpp, log4cxx or simple logging to files or console. . Tntnet is fully multithreaded and much work has been gone into making it scalable. It uses a dynamic pool of worker threads, which answer requests from HTTP clients.
PackageMaintainer	Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com>
PackageName	libtntnet-dev
PackageSection	libdevel
PackageVersion	2.2.1-2
SHA-1	0B8E51848E9F8FE287AF95DA3F0C9192C50F9777
SHA-256	564658358BC168AC70893949962DF12838F4322CEFA01A44E2AD7458CC20CC16

Key	Value
MD5	3450F07800890E8C6141777A641F831F
PackageArch	i586
PackageDescription	Headers and static library for tntnet development.
PackageMaintainer	umeabot <umeabot>
PackageName	libtntnet-devel
PackageRelease	11.mga9
PackageVersion	2.2.1
SHA-1	0C62A957BB9906514307B6ACAA7021708120772F
SHA-256	BC884C4BC2429AB8B3A431141947E5CC3EAF4341301B2F13BA1F867FDCADE86C

Key	Value
MD5	E2F225C8C63297A46DC1E82C27290F43
PackageArch	s390x
PackageDescription	Development files for tntnet
PackageMaintainer	Fedora Project
PackageName	tntnet-devel
PackageRelease	3.fc19
PackageVersion	2.2
SHA-1	0CD08397AB2D96B44E809D43A55E4F39F59453ED
SHA-256	B0ECC0081B6276CCBA99583D6D78B0E80267E704041F95BE2B446EA41B7A60B9

Key	Value
MD5	10396E740EA83971EB15465A0E5D7D0A
PackageArch	aarch64
PackageDescription	Development files for tntnet
PackageMaintainer	Fedora Project
PackageName	tntnet-devel
PackageRelease	4.fc22
PackageVersion	2.2.1
SHA-1	118FE1D94C3CD8C1B83BAA73B7A6964D1B28BC1F
SHA-256	05DBCC7C3DC8774F007A0B721C13D6A9174C55FF8A92C9E97BF04EF8B51E6039

Key	Value
MD5	6485BDC0DC0A7146C13B8E70D54280C9
PackageArch	aarch64
PackageDescription	Development files for tntnet
PackageMaintainer	Fedora Project
PackageName	tntnet-devel
PackageRelease	10.fc24
PackageVersion	2.2.1
SHA-1	133BB5BC89382439935BFF6EDC7135A9FF9050F2
SHA-256	B6B5A0A1641D7578A2F2ACCBFD82F3B20CF7CBA35163A211BFBCCF139CB69589

Key	Value
FileSize	127210
MD5	4341F1620D45954706DD9938A8E0913C
PackageDescription	Tntnet library development headers Tntnet has a template-language called ecpp similar to PHP, JSP or Mason, where you can embed c++ code inside a HTML page to generate active content. The ecpp files are precompiled to C++ classes called components and compiled and linked into a shared library. This process is done at compiletime. The web server Tntnet needs only the compiled component library. . Because the web applications are compiled into native code, they are very fast and compact. . Components can call other components. So you can create building blocks of HTML parts and call them in other pages like subprocesses. . Requests are parsed by tntnet and the request information is easily accessible to the components. It supports GET and POST parameters and MIME multipart requests for file upload. . The template language has also support for internationalized applications. You can easily create web applications for different languages. . Other features are: cookies, HTTP upload, automatic request parameter parsing and conversion, automatic session management, scoped variables (application, request and session), internationalisation and keep-alive. . Logging is done through cxxtools, which provides a unique API for log4cpp, log4cxx or simple logging to files or console. . Tntnet is fully multithreaded and much work has been gone into making it scalable. It uses a dynamic pool of worker threads, which answer requests from HTTP clients.
PackageMaintainer	Kari Pahula <kaol@debian.org>
PackageName	libtntnet-dev
PackageSection	libdevel
PackageVersion	2.2.1-3+b1
SHA-1	1792E639FF5570B9CCFD75E7E86DC6CC86172DE4
SHA-256	D7DA0ED634CCF34AEB0BB9AF1D76724163AD40321AD7A71B4D7C5A7244AF8EB8

Key	Value
FileSize	131938
MD5	BF92C73B76F0C0FCC7D86870EA3D73AC
PackageDescription	Tntnet library development headers Tntnet has a template-language called ecpp similar to PHP, JSP or Mason, where you can embed c++ code inside a HTML page to generate active content. The ecpp files are precompiled to C++ classes called components and compiled and linked into a shared library. This process is done at compiletime. The web server Tntnet needs only the compiled component library. . Because the web applications are compiled into native code, they are very fast and compact. . Components can call other components. So you can create building blocks of HTML parts and call them in other pages like subprocesses. . Requests are parsed by tntnet and the request information is easily accessible to the components. It supports GET and POST parameters and MIME multipart requests for file upload. . The template language has also support for internationalized applications. You can easily create web applications for different languages. . Other features are: cookies, HTTP upload, automatic request parameter parsing and conversion, automatic session management, scoped variables (application, request and session), internationalisation and keep-alive. . Logging is done through cxxtools, which provides a unique API for log4cpp, log4cxx or simple logging to files or console. . Tntnet is fully multithreaded and much work has been gone into making it scalable. It uses a dynamic pool of worker threads, which answer requests from HTTP clients.
PackageMaintainer	Kari Pahula <kaol@debian.org>
PackageName	libtntnet-dev
PackageSection	libdevel
PackageVersion	2.2.1-3+b1
SHA-1	1E5FAF149546556846FAB0ACB961410182560D8E
SHA-256	99DBA74FFF1D5CE1E98EE6CE5923CE81F2F6C10A157D8ECD4BBD020257344786

Key	Value
FileSize	137460
MD5	A754847BE32A5B8254855929EFE57936
PackageDescription	Tntnet library development headers Tntnet has a template-language called ecpp similar to PHP, JSP or Mason, where you can embed c++ code inside a HTML page to generate active content. The ecpp files are precompiled to C++ classes called components and compiled and linked into a shared library. This process is done at compiletime. The web server Tntnet needs only the compiled component library. . Because the web applications are compiled into native code, they are very fast and compact. . Components can call other components. So you can create building blocks of HTML parts and call them in other pages like subprocesses. . Requests are parsed by tntnet and the request information is easily accessible to the components. It supports GET and POST parameters and MIME multipart requests for file upload. . The template language has also support for internationalized applications. You can easily create web applications for different languages. . Other features are: cookies, HTTP upload, automatic request parameter parsing and conversion, automatic session management, scoped variables (application, request and session), internationalisation and keep-alive. . Logging is done through cxxtools, which provides a unique API for log4cpp, log4cxx or simple logging to files or console. . Tntnet is fully multithreaded and much work has been gone into making it scalable. It uses a dynamic pool of worker threads, which answer requests from HTTP clients.
PackageMaintainer	Kari Pahula <kaol@debian.org>
PackageName	libtntnet-dev
PackageSection	libdevel
PackageVersion	2.2.1-4
SHA-1	1F8AE9AE8D67AE011E799340E2D6AC10306ABCE9
SHA-256	F993853995FAB508B8BBE7FCB68A0EFBF1738160772BA85AECF21CD7F660F1E3