tntnet 2.2.1-2 source package in Ubuntu
Changelog
tntnet (2.2.1-2) unstable; urgency=medium * Bump library package name to 12v5 for C++ ABI transition. (Closes: #796721) * Bump Standards-Version to 3.9.6 (No changes necessary) -- Kari Pahula <email address hidden> Sat, 05 Sep 2015 18:57:54 +0300
Upload details
- Uploaded by:
- Kari Pahula
- Uploaded to:
- Sid
- Original maintainer:
- Kari Pahula
- Architectures:
- any all
- Section:
- httpd
- Urgency:
- Medium Urgency
See full publishing history Publishing
Series | Published | Component | Section | |
---|---|---|---|---|
Xenial | release | universe | web |
Downloads
File | Size | SHA-256 Checksum |
---|---|---|
tntnet_2.2.1-2.dsc | 2.0 KiB | 90b331eddc4cee09b53e9c089cc9de4b24e6b5ecdbc53456d684d8aa4cf10934 |
tntnet_2.2.1.orig.tar.gz | 1.1 MiB | c83170d08ef04c5868051e1c28c74b9562fe71e9e8263828e755ad5bd3547521 |
tntnet_2.2.1-2.debian.tar.xz | 40.4 KiB | 69f9940757a2a85a83cee8d9110a7dc59a52d81cf77fb6a73b6c22feab32141e |
Available diffs
No changes file available.
Binary packages built by this source
- libtntnet-dev: No summary available for libtntnet-dev in ubuntu yakkety.
No description available for libtntnet-dev in ubuntu yakkety.
- libtntnet-dev-dbgsym: debug symbols for package libtntnet-dev
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: 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: debug symbols for package libtntnet12v5
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: 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 package 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: 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 package tntnet-demos
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-doc: No summary available for tntnet-doc in ubuntu zesty.
No description available for tntnet-doc in ubuntu zesty.
- tntnet-runtime: No summary available for tntnet-runtime in ubuntu yakkety.
No description available for tntnet-runtime in ubuntu yakkety.
- tntnet-runtime-dbgsym: No summary available for tntnet-runtime-dbgsym in ubuntu yakkety.
No description available for tntnet-
runtime- dbgsym in ubuntu yakkety.