Parents (Total: 21)

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

Key	Value
FileSize	220862
MD5	58E01DB512BD4FDF57975ADE24F042C5
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	libtntnet12
PackageSection	libs
PackageVersion	2.2.1-1
SHA-1	054CE868E222E9BFB6F69AE9BC99F1147DDE33DB
SHA-256	10E6E444BFF257E331E945424636934A31969B48C8C3C949C41FED679CD3984A

Key	Value
FileSize	227642
MD5	216BF63539DC838B7585C4311F503845
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	libtntnet12
PackageSection	libs
PackageVersion	2.2.1-1
SHA-1	1657C6E9F105450B3AF5E4EFBEC9C2A5249F5B90
SHA-256	ACE8C982F80F6163C86E840C5329EB02A4F044020E3C1053FEA0E8F679A77D94

Key	Value
FileSize	246780
MD5	2EBB9AB9B5E3E9A28D83AFF78AD9AEA6
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-1
SHA-1	1ACE0F224ECE7086867A8E0565E98C7CF6E90574
SHA-256	0EC20B07F2F2249375B7910142E3235E58FF970DF912671C7D22299A19BE93BE

Key	Value
FileSize	63532
MD5	E7F259AAD5E2C07B34E381CE7923E74D
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-1
SHA-1	1F0BD1DDCE650FF24E67F40547B2B0ADADC62DC3
SHA-256	178AB10A2DFF630B4A826FD9F09F980605D1DBFC320B67F034DDD523F52305EA

Key	Value
FileSize	259974
MD5	106F83B7B87DC31CD12B2F56544AAB41
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	libtntnet12
PackageSection	libs
PackageVersion	2.2.1-1
SHA-1	3DF343A1AB17F5728B35E7E0A8B6B019AD6493ED
SHA-256	44F84B4E4FF0F098ABDEC49A2C5A9884AC12EAEF4672D77F3C4A13B491D6E042

Key	Value
FileSize	68254
MD5	892A95A6155C576487C9D0CAF15A4A07
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-1
SHA-1	430BD32713CD243DA66762148ABA5AE1AF967223
SHA-256	F6451307731EBE85159E4FB78B95968CC51D114B31167D49470E58C6E7EFD2E8

Key	Value
FileSize	119002
MD5	F5C3AEC7D5C3D518015A9A6C30EA8B99
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-1
SHA-1	460B0563AC49A953B6B5389A3CC0AD54AF65CC56
SHA-256	E7B2E8DBA9517003BBF2A0E927316674CBA93D6A813C30AFC6945B4BFDD37DF8

Key	Value
FileSize	475196
MD5	35620118D505991DD9B95F13BAC8574E
PackageDescription	documentation 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-doc
PackageSection	doc
PackageVersion	2.2.1-1
SHA-1	5B749E677EE80D73D74AAC68E95E0479B4F6858F
SHA-256	B9BBE6CC75F4D4CC54FF8EC81BCB715D6855FC3B8D1D1977113B864C3CF034B8

Key	Value
FileSize	121704
MD5	281DCA9BBDF497869F7AEDD6E1132912
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-1
SHA-1	7D5AB00DF1877DDE4236970EE3D031B5803D627D
SHA-256	D35478CA31CF8DF755AFDA67B2067336770467BF645A61206A1D288FAFA732D7

Key	Value
FileSize	59216
MD5	3DF5BB9D41271E3C25D540AC7FCA04F0
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-1
SHA-1	80360CDA3207D3554D4DCA0305ACE236B1B10172
SHA-256	5813563354C053EFEB3719B8B5338AEA90B620A5FA4B8143CA88E8BB0599B61B