TUX module implementation (was RE: How to specify a particular user module to handle a specific httprequest?)

["Robert S. Nasby" <rnasby shnaz com>]

What I would really like to see is a way to specify module(s) which would be
called for a particular list of extensions, as well as a list of module(s)
which would be called for all requests (with a way to specify what order
modules are called, as well as a whether a module was called before
extension-specific modules or after (ala pre-routing or post-routing in
iptables)).  This would allow things like SSI processing, referer
decision-branching, scripting languages, etc. to more easily be implemented
on TUX.

I have no idea how significant of a change would be required to implement
this, but I think it would increase TUX's acceptance as a viable alternative
to Apache.

On the flipside, would I be correct in assuming that such processing of all
requests would significantly affect TUX's main performance gains (no longer
can do direct file-to-NIC transfers, requires at least two context switches
for each request)?

I would be interested in hearing other opinions about this subject.

Thanks,

Rob Nasby

-----Original Message-----
From: tux-list-admin@redhat.com [mailto:tux-list-admin@redhat.com]On Behalf
Of Valkanas Nikos
Sent: Thursday, March 21, 2002 3:48 AM
To: tux-list@redhat.com
Subject: RE: How to specify a particular user module to handle a specific
httprequest?


Both Rob and Liang are right. I don't expect TUX to gain significant
acceptance unless it can supplement services offered by mainstream web
servers (like apache) in a similar way, transparent to the client. The
client will not commit to write different code for unproven servers. If that
server flops in a couple of years, what's one to do with his code? In
addition the particular method has very serious shortcomings (i.e. cannot
use post variables with a module).

I don't think that redirecting traffic, i.e php to apache, is the solution
either. I think that redirection is slower than a direct connection to
apache. Therefore all benefits offered by TUX (mainly speed) are negated in
a site that has 95% dynamic content (very usual in ecommerce or database
content driven sites).

I am trying to work on that change for TUX, but I have very little precious
spare time to go. Hopefully Ingo will see wisdom in this, possibly raise its
priority. Myself I still have problems figuring out how TUX works. strace -f
gives me some good overall feeling. However for a good knowledge, I would
need to use gdb. I have found it very difficult to use it on multiple
processes, with kernel space code. Any debugging advise would be greatly
appreciated. I expect that 2 weeks from now I will find so more free time to
take another crack at it.

Nikos

> -----Original Message-----
> From: Liang Yang [mailto:Liang.Yang@asu.edu]
> Sent: Thursday, March 21, 2002 5:17 AM
> To: tux-list@redhat.com
> Subject: RE: How to specify a particular user module to
> handle a specific httprequest?
>
>
> Hi,
>
> Thank you.
>
> What you mean all request will be sent to the first module? If I want
> the first module to only resposnd to the graphic file request
> from client,
> can Apache still receive all the other requests from client
> if I redirect
> them to Apache(on port 8080)?
>
> If the first module accpet the client graphic file
> request(suppose user
> want to get demo.jpg file on the server? Should the
> http://server/demo.jpg
> will result in the action of first.tux?   what's the correct
> URL format?
> http://server/module.tux doesn't include any graphic file information
> client want to get.
>
> Liang
>
> -----Original Message-----
> From: tux-list-admin@redhat.com [mailto:tux-list-admin@redhat.com]On
> Behalf Of Robert S. Nasby
> Sent: Wednesday, March 20, 2002 7:27 PM
> To: tux-list@redhat.com
> Subject: RE: How to specify a particular user module to handle a
> specific http request?
>
>
> You can't specify modules like that.  tux must be set up to
> either send ALL
> request to one specific module (the first one on the list),
> or call modules
> via the URL (as in http://www.mydomain.com/module.tux).
> There is currently
> no way to specify module1.tux handle *.jpg documents, while
> module2.tux
> handle *.mpg documents.  this is a feature I would personally
> like to see
> included, but this would involve a change in the fundamental
> way tux handles
> requests.
>
> Rob Nasby
>
> -----Original Message-----
> From: tux-list-admin@redhat.com
[mailto:tux-list-admin@redhat.com]On Behalf
Of Liang Yang
Sent: Monday, March 18, 2002 12:52 PM
To: tux-list@redhat.com
Subject: How to specify a particular user module to handle a specific http
request?


Hi,

If I want to use my user module to handle some specific http request
(for example, requests for big graphic file), I know I need to add MIME type
in /etc/tux.mime.types(add a line such as "image/jpeg     jpg jpeg jpe"),
but I don't know how to specify a particular module to handle this kind of
request if I loaded multiple user modules at the same time.Suppose I loaded
demo.tux, demo2.tux,demo3.tux when starting TUX, but I only want demo.tux
to hanlde graphic file request, I don't want other user modules to be
involved.
How can I do it?

/etc/tux.mime.types doesn't contain the corresponding parameter to specify
a particular user module to hadle a particular mime type files, the
reference
manual just says "all extensions listed after TUX/module will be handled by
TUX userspace modules".

BTW, I can use http://localhost/demo.tux to invoke my user module demo.tux,
but if I specify
only demo.tux to handle http request about .jpg file, should the URL
http://localhost/sample.jpg
work and also result in "hello webworld" in the screen just like
http://localhost/demo.tux ?

Sometimes I feel I really need help from TUX experts since I can hardly find
any useful documents
about TUX in Internet  :-)

Liang



_______________________________________________
tux-list mailing list
tux-list@redhat.com
https://listman.redhat.com/mailman/listinfo/tux-list



_______________________________________________
tux-list mailing list
tux-list@redhat.com
https://listman.redhat.com/mailman/listinfo/tux-list



_______________________________________________
tux-list mailing list
tux-list@redhat.com
https://listman.redhat.com/mailman/listinfo/tux-list



_______________________________________________
tux-list mailing list
tux-list@redhat.com
https://listman.redhat.com/mailman/listinfo/tux-list