Key | Value |
---|---|
FileName | ./usr/share/doc/tntnet-doc/demos/newsdb/newsdb.sql |
FileSize | 244 |
MD5 | DCEBB9C10D09E21D49E60F9EE4D9C088 |
SHA-1 | 0B6F991EDA24C4B37209E85A27F6495E1F2A633E |
SHA-256 | 2ACCAB2352CDE082EA62FF10176E3B749FDC6B9486D04D95F76109812A3BCF90 |
SSDEEP | 6:vQyHAsKuQrqRJzilQ7zzilQQgv63emFdZdPoXRya:IyHA9Tq3iMiGoe+ZyRN |
TLSH | T164D0C75D90A01F10F1E121010BD535E077D9FD4B1B98BBB244C4DD1E566874754FA735 |
hashlookup:parent-total | 7 |
hashlookup:trust | 85 |
The searched file hash is included in 7 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
FileSize | 474186 |
MD5 | 82E3AEB4110F99A1AE03C7123B7051DB |
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-3 |
SHA-1 | CA0463455C4DFCFD00C218F3C5A8B61C4D2AC7FC |
SHA-256 | 033C544785DE6AFA6727FF51B3EB23A155780D118CD317A71CE9A5A07B18A4DD |
Key | Value |
---|---|
FileSize | 459748 |
MD5 | E47BB2D4B1AA2807F7D907A548BE02F9 |
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 | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | tntnet-doc |
PackageSection | doc |
PackageVersion | 2.2.1-4build1 |
SHA-1 | 2BEA565DA2E29C8331F830681C5DAE04D236B88D |
SHA-256 | 647895938641D99B97C325877974EA15374E8D9F32BC9AFF3970DAFFA3398903 |
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 | 461052 |
MD5 | 5C15C36C1B00F0911AD41C6A6FFCF739 |
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 | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | tntnet-doc |
PackageSection | doc |
PackageVersion | 2.2.1-2 |
SHA-1 | 525C87A3107519305BFDA66D5790858A4105882D |
SHA-256 | 547CC5A889434F90BA051CF6B58B1F7B3EA6DDE6C08F440414D218FEA119D1B5 |
Key | Value |
---|---|
FileSize | 473492 |
MD5 | 01205A25A97E1CB7F04F6E3A071BF7F1 |
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-4 |
SHA-1 | 9CF895157B1A697C6D6B1AB1D29001CA3CE17886 |
SHA-256 | 2AA5966372860434F4AF54D79CCB66F6E7FEF04BDFE6DFB3BD5A563555AC9731 |
Key | Value |
---|---|
FileSize | 462094 |
MD5 | C88C288DB02BE2F2AF9AD7CB1738C6E6 |
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 | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | tntnet-doc |
PackageSection | doc |
PackageVersion | 2.2.1-1 |
SHA-1 | 1D5B9887A5FE9DDE2DAC65BF7FB61FF25F082EED |
SHA-256 | 52A74CEEDBBA3A2812E2CDBD8040B484249C2E84EA2D3BC901436409A24BBF4F |
Key | Value |
---|---|
FileSize | 459692 |
MD5 | 503DFF7AC44A1E195D8DDD670C9841DE |
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 | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | tntnet-doc |
PackageSection | doc |
PackageVersion | 2.2.1-3build1 |
SHA-1 | 03B83C6FDA8EE273F8B330A0A8814066896C213A |
SHA-256 | A99EEB2B970FD7BE80AB8F4E926E6BAB1C7566C680B1CE0D721EB17C96B8471F |