Key | Value |
---|---|
FileName | ./usr/share/man/man1/ecppc.1.gz |
FileSize | 1637 |
MD5 | 13D9A7134EBE67787955F061F4E6ED87 |
SHA-1 | 03073F454CC9EFAD12C113DC1577674960DE7724 |
SHA-256 | 56275C3002F6E9C8B702DF3C71141966FBC4C16E6798C0417C962199C7FDAB0F |
SSDEEP | 48:XT/FtwMciteTPFNaBannUaxTyzholLGDfbaB:D/FtwDitGtqGnUaxTZyOB |
TLSH | T15731C8F86D9C423D99AD4E3C185A284C05A36B6B01DF5FB654059DB438A8501296ABEC |
hashlookup:parent-total | 54 |
hashlookup:trust | 100 |
The searched file hash is included in 54 parent files which include package known and seen by metalookup. A sample is included below:
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 |
---|---|
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 | 117946 |
MD5 | 873E6F4C208BA2978FE0120C81AE4A83 |
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 | Ubuntu Developers <ubuntu-devel-discuss@lists.ubuntu.com> |
PackageName | libtntnet-dev |
PackageSection | libdevel |
PackageVersion | 2.2.1-2 |
SHA-1 | 0B8E51848E9F8FE287AF95DA3F0C9192C50F9777 |
SHA-256 | 564658358BC168AC70893949962DF12838F4322CEFA01A44E2AD7458CC20CC16 |
Key | Value |
---|---|
FileSize | 127210 |
MD5 | 4341F1620D45954706DD9938A8E0913C |
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 | 1792E639FF5570B9CCFD75E7E86DC6CC86172DE4 |
SHA-256 | D7DA0ED634CCF34AEB0BB9AF1D76724163AD40321AD7A71B4D7C5A7244AF8EB8 |
Key | Value |
---|---|
MD5 | 1EAA8EA9DB6C449D8ABA8AFBD68A1DB9 |
PackageArch | armv7hl |
PackageDescription | A web application server for web applications |
PackageMaintainer | Fedora Project |
PackageName | tntnet |
PackageRelease | 20.fc33 |
PackageVersion | 2.2.1 |
SHA-1 | 1A4C09A238B52EE09B46AC90ECD62EFA4CE7A5D1 |
SHA-256 | 8D91DAC9570976B9012F93409E728631AB2709D78F808F98FD85DCE69D002439 |
Key | Value |
---|---|
MD5 | 9CC80310E3CDE52048955F9ADC3BFE59 |
PackageArch | s390x |
PackageDescription | A web application server for web applications |
PackageMaintainer | Fedora Project |
PackageName | tntnet |
PackageRelease | 4.fc22 |
PackageVersion | 2.2.1 |
SHA-1 | 1BD486B0CC960639944F54242EC60E60C341D428 |
SHA-256 | 044CDFF7A0B8A0C6291B5E38FB31512DBEB331581140E4E138FCCCC7F4708DCD |
Key | Value |
---|---|
MD5 | 6A9892ED323DEFC023AC0DC6FBA00A43 |
PackageArch | i686 |
PackageDescription | A web application server for web applications |
PackageMaintainer | Fedora Project |
PackageName | tntnet |
PackageRelease | 19.fc32 |
PackageVersion | 2.2.1 |
SHA-1 | 1DA198FB7C2A73D79DA3D1F5830D372321A3C999 |
SHA-256 | A3B409B4D180580CB43B6F87D99212679F72B11B1D942A86BCE8BDE4E8EF189B |
Key | Value |
---|---|
FileSize | 131938 |
MD5 | BF92C73B76F0C0FCC7D86870EA3D73AC |
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 | 1E5FAF149546556846FAB0ACB961410182560D8E |
SHA-256 | 99DBA74FFF1D5CE1E98EE6CE5923CE81F2F6C10A157D8ECD4BBD020257344786 |
Key | Value |
---|---|
FileSize | 137460 |
MD5 | A754847BE32A5B8254855929EFE57936 |
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 | 1F8AE9AE8D67AE011E799340E2D6AC10306ABCE9 |
SHA-256 | F993853995FAB508B8BBE7FCB68A0EFBF1738160772BA85AECF21CD7F660F1E3 |
Key | Value |
---|---|
MD5 | 061C6387F9CC8096538EF588984CC8C0 |
PackageArch | s390x |
PackageDescription | A web application server for web applications |
PackageMaintainer | Fedora Project |
PackageName | tntnet |
PackageRelease | 7.fc20 |
PackageVersion | 2.2 |
SHA-1 | 213BC66585F4148A67A972DAB3FD419E4CA6CADA |
SHA-256 | 9C12F9674148A55E3240D90C0D200E5372B96B18E8968D82AE2B95DA04D67119 |