From: dave.joubert on
Hi,
I am working on several projects (some only in my head) and a lot of
them depend on being able to get easy predictable access to user's PC.
I do not want to explain firewalls, NAT etc to the user, so I have
come up with a solution that will allow me to run a webserver on the
user's machine. The webserver will start life as tclhttpd and I will
probably add things like WebDAV, execution paths, dbus, etc to it.

My solution consists of 3 pieces, two of which are public and can be
used by anybody at all; ie I am currently hosting them and you are
welcome to use them.

To use the public infrastructure, download the private proxy server,
modify it as you wish and run it on your client machine to connect to
a standard http server on your client machine (or if fact any machine
your private proxy can reach!!)

Voila: you can tell aunt Mandy the photos are available at at
Jon.httptun.net and today's password is kittykat!

The full description is at http://www.httptun.net/

This is Alpha code, ie it works, displays lots of debug messages and
has not been tested on lots of platforms.

Dave
From: ddd on
On Sun, 7 Mar 2010 10:04:50 -0800 (PST), dave.joubert(a)googlemail.com
<dave.joubert(a)googlemail.com> wrote:
> Hi,
> I am working on several projects (some only in my head) and a lot of
> them depend on being able to get easy predictable access to user's PC.
> I do not want to explain firewalls, NAT etc to the user, so I have
> come up with a solution that will allow me to run a webserver on the
> user's machine. The webserver will start life as tclhttpd and I will
> probably add things like WebDAV, execution paths, dbus, etc to it.
>
Hi Dave,

Nice project! Can you tell why you are using tclhttpd as a base? And if
it is working well for you? And have you considered something simpler like
wibble or a non tcl server?

thanks.
From: dave.joubert on
On Mar 9, 12:31 pm, ddd <d...(a)ddd.dd> wrote:
>
> Hi Dave,
>
> Nice project!  Can you tell why you are using tclhttpd as a base?  And if
> it is working well for you?  And have you considered something simpler like
> wibble or a non tcl server?
>
> thanks.

Thanks.

I am extremely undecided about the HTTP server and I have been looking
at the small servers on http://wiki.tcl.tk/602
The kicker was WebDAV - none of them support it, and tclhttpd has only
partial support.

Criteria:
Small
8.5 for maximum compatibility
Authentication and SSL - one certainly would not like Joe Random
Stranger to execute things on one's machine
WebDAV

I have several ideas about WebDAV support, including adding proxying
capability to whatever server I choose, and then passing the WebDAV
stuff on to say Apache...

a Small neat solution would allow me to actually meld my current proxy
code and the new server into one.

Dave

From: dave.joubert on
On Mar 9, 1:32 pm, "dave.joub...(a)googlemail.com"
<dave.joub...(a)googlemail.com> wrote:
> a Small neat solution would allow me to actually meld my current proxy
> code and the new server into one.
>
> Dave

Of course, one could also take Wibble (or any of the slightly larger
solutions on http://wiki.tcl.tk/602 ) and merge my proxy code into
that instead. It was just easier to write the proxy code standalone
first (esp if one cannot decide which server one prefers).

Dave