1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
|
Source: tntnet
Section: web
Priority: extra
Maintainer: Kari Pahula <kaol@debian.org>
Build-Depends: cdbs, debhelper (>= 5), libcxxtools-dev, quilt, automake1.9, libgnutls-dev, libltdl3-dev
Standards-Version: 3.7.2
Package: tntnet
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Provides: httpd, httpd-cgi
Description: 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.
.
Homepage: http://www.tntnet.org/
Package: tntnet-doc
Architecture: all
Section: doc
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: 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.
.
Homepage: http://www.tntnet.org/
Package: tntnet-demos
Architecture: any
Section: doc
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: 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.
.
Homepage: http://www.tntnet.org/
Package: libtntnet5
Architecture: any
Section: libs
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: 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.
.
Homepage: http://www.tntnet.org/
Package: libtntnet-dev
Architecture: any
Section: libdevel
Depends: ${shlibs:Depends}, ${misc:Depends}, libcxxtools-dev
Conflicts: tntnet (<< 1.5.1+1.5.2pre3-3)
Description: 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.
.
Homepage: http://www.tntnet.org/
|
