Orchid XP v8 a écrit :
>> Or better still, launch shttpd with the appropriate option telling it 
>> that .exe are CGI files:
>>
>> shttpd -cgi_ext "exe"
> 
> Also tried that and it didn't work.
> 
> The hack above does, however, work.
> 

OK, so that's one more reason for me to keep running Linux I guess, 
where it works fine and starts instantaneously :-)

Maybe you should throw a note to the author though, perhaps the 
behaviour on Windows is not what's intended...

-- 
Vincent

Post a reply to this message

Warp wrote:

>   You got a web server and you didn't install it? How can that work?

You put the executable file in a directory, double-click it, and it 
runs. Nothing to install, nothing to uninstall afterwards. And only a 
few hundred KB too. Which is basically what I was looking for...

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message

Orchid XP v8 wrote:
> Warp wrote:
> 
>>   You got a web server and you didn't install it? How can that work?
> 
> You put the executable file in a directory, double-click it, and it 
> runs. Nothing to install, nothing to uninstall afterwards. And only a 
> few hundred KB too. Which is basically what I was looking for...
> 
So you've installed it. OTOH you haven't needed to configure it or your 
system.

John

-- 
"Eppur si muove" - Galileo Galilei

Post a reply to this message

Orchid XP v8 <voi### [at] devnull> wrote:
> Warp wrote:

> >   You got a web server and you didn't install it? How can that work?

> You put the executable file in a directory, double-click it, and it 
> runs. Nothing to install, nothing to uninstall afterwards. And only a 
> few hundred KB too. Which is basically what I was looking for...

  We clearly have completely different definitions of "installing a
program".

-- 
                                                          - Warp

Post a reply to this message

Warp wrote:

>   We clearly have completely different definitions of "installing a
> program".

Yes.

To me, if you can use a program just by running it, that's not 
"installing" it.

If, however, you have to insert DLLs into particular folders, create 
registry keys and configure environment variables, that's "installing" 
something.

The former means you can just drop the binary only (say) a USB flash 
drive and use it anywhere. The latter means that you have to do some 
setup (and probably removal) at every PC.

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message

Orchid XP v8 <voi### [at] devnull> wrote:
> Warp wrote:

> >   We clearly have completely different definitions of "installing a
> > program".

> Yes.

  My definition of "installing" is clear and unambiguous. Your definition
is rather fuzzy.

> To me, if you can use a program just by running it, that's not 
> "installing" it.

> If, however, you have to insert DLLs into particular folders, create 
> registry keys and configure environment variables, that's "installing" 
> something.

  What if it doesn't install DLLs but creates registy keys and configures
environment variables? Is it then installing? What if it doesn't configure
environment variables? Is it still installing? What if it installs DLLs
but doesn't create a registry key?

> The former means you can just drop the binary only (say) a USB flash 
> drive and use it anywhere. The latter means that you have to do some 
> setup (and probably removal) at every PC.

  But you didn't "drop the binary only a USB flash drive" (whatever that
may mean). You installed it in your system.

-- 
                                                          - Warp

Post a reply to this message

I've used thttpd in a number of embedded systems. Seems to do the job well
and is a single executable.

-- Chris

Post a reply to this message

Orchid XP v8 wrote:
> I had a look here this morning. Sadly, almost everything requires you to 
> "install" it before you can use it. I was hoping for a single executable 
> solution.

http://www.tcl.tk/software/tclhttpd/

The TclHttpd Starkit distribution includes the server code, the required 
TclLib modules, and a sample document tree in a single file for easy 
deployment. Just run the starkit with the TclKit interpreter. It takes 
all the same command line arguments as bin/httpd.tcl. Using the sdx tool 
that wraps and unwraps Starkits, you can assemble your own custom 
TclHttpd application Starkit.

-- 
Darren New / San Diego, CA, USA (PST)

Post a reply to this message

Orchid XP v8 wrote:

> OK, *finally*...
> 
> Create a small file called Foo.cgi that simply contains the line
> 
>   #!Foo.exe
> 
> and *at last* the server does what I want it to!

Now I'm confused! I just tried this at work... and it fails. WTF?

Post a reply to this message

Chris Cason wrote:
> I've used thttpd in a number of embedded systems. Seems to do the job well
> and is a single executable.

Unfortunately, I can't find a precompiled Windows binary anywhere...

Post a reply to this message