Key | Value |
---|---|
FileName | ./usr/share/doc/tntnet-doc/demos/chat/sad.png |
FileSize | 474 |
MD5 | 9ED6D13309F8E31145319FA87A4C5CE2 |
SHA-1 | 27FC173587CF7A60D3A21C4CA0323F29F6EF6138 |
SHA-256 | 6878771E22594C9124B8E45AFCE369A8B8A7C6374DF53B499A57F7EDB7413A65 |
SSDEEP | 12:6v/7LL+GEaVLsL1qAMmgyNxK1EtTXiJhud:SL+CYMbyjXhkEd |
TLSH | T170F05CE0A7CEBCB8E62E047CC038E88AE73008F0B874BC0418E90082A2320CE73C02C1 |
hashlookup:parent-total | 30 |
hashlookup:trust | 100 |
The searched file hash is included in 30 parent files which include package known and seen by metalookup. A sample is included below:
Key | Value |
---|---|
FileSize | 240176 |
MD5 | 2B8BB43AF5FEFFB3CA8EE98D43D6C448 |
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-4 |
SHA-1 | 02EB967F9BEA8102426FF20C5F99753EA9FFC1DE |
SHA-256 | 03E6FEA8DD3F65D24E6749312F08A6370E014AC8E882E8095DBC3CAD96BDE916 |
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 |
Key | Value |
---|---|
FileSize | 219188 |
MD5 | EE588C8555BAB6445E8F1D4B682CBCBD |
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-4 |
SHA-1 | 12E628A88BB1355E2262C347D04F523B4D0815F1 |
SHA-256 | 6261F7FF0171AD6046E3C8686AC7A2FE0BDCCE809FEDB1AB926F27486F3DC533 |
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 | 233672 |
MD5 | ADE24560FEF6A7D025ED2AC7819E8279 |
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 | 1AF939DDE05AD66BC93A53053D6C8A0F45093FA7 |
SHA-256 | A9A0C0C958C884B7F3EB76FA448A9F3E8244FB66497D1FD420DDE0769C7B52C1 |
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 | 230592 |
MD5 | 364E033C9B5227FEB7844651CCB534B4 |
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 | 1E3727DCB4873D322D9065092CE66D95DC90CA72 |
SHA-256 | E074C8061A61855DBD9E0D9E23B8A3930B3B81CE147A4B29005833700745C5B7 |
Key | Value |
---|---|
FileSize | 220632 |
MD5 | 47C3F1FE2C432A3753F2A9D5459864A4 |
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-4 |
SHA-1 | 26EAB81627A091E395414CB9388EEC33036AE305 |
SHA-256 | 9DFF79EC13F2943855E3CF68F86C8C822D5BF5A6195AC895C1BCC3FEC843686E |
Key | Value |
---|---|
FileSize | 237720 |
MD5 | 81035980C623F70DA9DDF7FAF7F3CAFB |
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-4 |
SHA-1 | 2874F612A40E3068A3BA4D110C79038EED702685 |
SHA-256 | 1CC27A73046E66813F0892AA87040B6F049EBC48C7B1A435A10DD52F08B5FB1F |
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 |