tntnet 2.2.1-3build1 source package in Ubuntu
Changelog
tntnet (2.2.1-3build1) bionic; urgency=high * No change rebuild against openssl1.1. -- Dimitri John Ledkov <email address hidden> Mon, 05 Feb 2018 16:54:51 +0000
Upload details
- Uploaded by:
- Dimitri John Ledkov
- Uploaded to:
- Bionic
- Original maintainer:
- Ubuntu Developers
- Architectures:
- any all
- Section:
- web
- Urgency:
- Very Urgent
See full publishing history Publishing
Series | Published | Component | Section | |
---|---|---|---|---|
Bionic | release | universe | web |
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
tntnet_2.2.1.orig.tar.gz | 1.1 MiB | c83170d08ef04c5868051e1c28c74b9562fe71e9e8263828e755ad5bd3547521 |
tntnet_2.2.1-3build1.debian.tar.xz | 40.5 KiB | fbb7e8f45cb184644b0370c29f34d8dd240b24266563183fcf111637cacc35af |
tntnet_2.2.1-3build1.dsc | 1.8 KiB | fd785e9ca2586b8ea73b342fc3baeaf6166407dc54742c87bdc4a4c157a0a1f6 |
Available diffs
- diff from 2.2.1-3 (in Debian) to 2.2.1-3build1 (597 bytes)
Binary packages built by this source
- libtntnet-dev: No summary available for libtntnet-dev in ubuntu cosmic.
No description available for libtntnet-dev in ubuntu cosmic.
- libtntnet-dev-dbgsym: debug symbols for libtntnet-dev
- libtntnet12v5: 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.
- libtntnet12v5-dbgsym: No summary available for libtntnet12v5-dbgsym in ubuntu eoan.
No description available for libtntnet12v5-
dbgsym in ubuntu eoan.
- tntnet: 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.
- tntnet-dbgsym: debug symbols for tntnet
- tntnet-demos: 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.
- tntnet-demos-dbgsym: debug symbols for tntnet-demos
- tntnet-doc: 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.
- tntnet-runtime: Tntnet runtime system
This package has the runtime system for tntnet web server.
- tntnet-runtime-dbgsym: debug symbols for tntnet-runtime