Key | Value |
---|---|
FileName | snap-hashlookup-import/usr/share/doc/libtntnet12v5/AUTHORS |
FileSize | 35 |
MD5 | 57A2D7184B2FD662F74D54C6184B8ABB |
SHA-1 | C2E9646E6BC1E06934F9909DB9398B7EDCD3ED4F |
SHA-256 | F817259505791245A509D43CF667352B5D9D5F931EBCE53C14E4C1DB20B1E609 |
SHA-512 | 25BA76822AC76D286E57726A32E7FA5F212F328A0DDFC1AC0EF9ACB00B5F0C76909FA5FB46DD46AF3A6B51DE4A001B7017F99E16D056D0DD49F683876BD9CF8F |
SSDEEP | 3:GggK5CD:7wD |
TLSH | |
insert-timestamp | 1728291646.7009435 |
mimetype | text/plain |
source | snap:98OsNqE6FunyqVYl6gxnFV5KtweZoG4K_46 |
hashlookup:parent-total | 174 |
hashlookup:trust | 100 |
The searched file hash is included in 174 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 | 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 | 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 | 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 | 60922 |
MD5 | 35E72A7B30F0D33E4A284F69164BDACC |
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 | 0550F06B024E6CCD47008A6EE379A5CE9FC7EFB4 |
SHA-256 | 222DCC816D10558649532E271F6AE9E3CA4A51D884F668BA954F3B42C8B9E61B |
Key | Value |
---|---|
MD5 | 0B374EE628E3791ABD5EF588DB2A56C7 |
PackageArch | s390 |
PackageDescription | A web application server for web applications |
PackageMaintainer | Fedora Project |
PackageName | tntnet |
PackageRelease | 8.fc23 |
PackageVersion | 2.2.1 |
SHA-1 | 06E08DD35D0DC781F5D0563DD538C8178894CD76 |
SHA-256 | C328F1B2D7A041DCF85FFA8D661F1AD68789CD831F4831D7B56589E1158347D0 |
Key | Value |
---|---|
FileSize | 64040 |
MD5 | 3C9DA3B842154844DD84FDA2EEC3A2FD |
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-4 |
SHA-1 | 071809F54AF8DDF2F5FD831011959D15202B7759 |
SHA-256 | C72F673AB84B43CDD97EBB3B079A87E1AE285FB3A1DDDC9D206FDFCB44BC2188 |
Key | Value |
---|---|
FileSize | 60818 |
MD5 | BF5B3386E5D9BC2DAE5881B194F2B5A6 |
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 | 07759AB10F3A0762E1940072E07BE35BCAE2A7AA |
SHA-256 | 36797D14952A00A6BE34914ED0EDCFA2342DFDEB15BAFF0F2B9E87FD89671064 |
Key | Value |
---|---|
FileSize | 71196 |
MD5 | 72B8F027068D02B570066EF7706EC490 |
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-4 |
SHA-1 | 077B0ACEF8C0B77ED7C1AFB3D15E6C5CEE392072 |
SHA-256 | B087704884A89831477946E8A58DB13A086EA2BE7603AEDEE8062748E598E02C |
Key | Value |
---|---|
FileSize | 228780 |
MD5 | 5E3CE4F32B6A6E02008361D9060B59E6 |
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-4 |
SHA-1 | 09135413451A4AB206323C11C1B25831DA7C203D |
SHA-256 | E410D99AC0EA8FB2FED7D1030A49040E902045CB033472143E2112E5DF2BBC52 |