Re: Re: Re: Browsers as stand-alone UI

Nothing wrong with your requirements, and nothing that is incompatible with "run your own web service."

Copy perl scripts and data files to this location, and make a link on the desktop that launches the main perl script. The main script can adjust @INC to use its own private stash of modules.
A perl script can bring up the user's IE with a simple statement: system("start/b http://localhost:2345/").
If your web service only accepts connections originating from localhost, it's not going to open up problems on the LAN or internet.
I haven't suggested you exploit any vulnerability to implement this.

It would be harder to decide when to stop, since the user's free to wander off and browse other pages, or close the IE session.

Update: Look into HTTP::Daemon for a start, but that's only one option. I'm sure there's others.

--
[ e d @ h a l l e y . c c ]

Comment on Re: Re: Re: Browsers as stand-alone UI Select or Download Code

Replies are listed 'Best First'.
Re: Re: Re: Re: Browsers as stand-alone UI by EvdB (Deacon) on Apr 08, 2004 at 08:30 UTC
Bear in mind though that any machine that allows ssh connections will also allows users to connect to any port as if they were on the local machine and tunnel it to their remote machine. They will need an ssh login though. Probably not a problem but it might still be worth having a username and password prompt on the web interface 'just in case'.	[reply]