Parents (Total: 5)

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

Key	Value
FileSize	60038
MD5	C02119DCE0139D4A5976CB19FF10DF88
PackageDescription	Tntnet runtime system This package has the runtime system for tntnet web server.
PackageMaintainer	Kari Pahula <kaol@debian.org>
PackageName	tntnet-runtime
PackageSection	httpd
PackageVersion	2.2.1-3+b1
SHA-1	18691052623179E1FBC56913D48897E91BCAA933
SHA-256	B5118447177FCB3804BF3649513AE11A275C3B0594C94A5BDCAAFEAE6206AF5E

Key	Value
FileSize	227064
MD5	26101C951B1BBFCA67FAF79C5768FFD5
PackageDescription	Tntnet libraries 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	libtntnet12v5
PackageSection	libs
PackageVersion	2.2.1-3+b1
SHA-1	83DA25F83F2C9B721BB404BD22EF604E534F64F6
SHA-256	B0D6241EA727D6D1F28514DF521CF92829E9DFA722A16600CDF0798CA462B3D5

Key	Value
FileSize	227752
MD5	580B31FADEBA67F403FD69DF62D009D4
PackageDescription	demo web applications for Tntnet 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	tntnet-demos
PackageSection	doc
PackageVersion	2.2.1-3+b1
SHA-1	B376FC5DAFCD83DB4396B37F7FF79376E301AA73
SHA-256	D22364BD1F80E0EB0DE2A96858370BDF27D0AE3206B271ED0A86D74651FCC509

Key	Value
FileSize	127132
MD5	75E3366C3983FADA8362D2D0F924054F
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	3AECDFB6EAC374E621844424245C9BEDADA4364F
SHA-256	B9D8FE2C258F2603A979207997248B4D12C6F27187C27E30137B05EE503AA23F

Key	Value
FileSize	67500
MD5	36F1271CA78DE24424B9AEFDC104451C
PackageDescription	modular, multithreaded web application server for C++ 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	tntnet
PackageSection	httpd
PackageVersion	2.2.1-3+b1
SHA-1	AE5AAB8D6BDA0663C15E12AC87E080C998FEB366
SHA-256	4F76E2590494B3D6875F46C1A1EBBA5B3EEE11412524988C60170243A6EE6066