I have been working on a similar idea for a client of mine.
We are interested in having a feature that allows a user to move
interchangeably between the WWW and the local disk(s). This is trivial for
HTML files or documents, but for running scripts (search engines, imagemap)
or parsing forms, there is not current method. One option which to me seems
non-ideal is to run a server in a loopback kind of mode on the local machine.
My idea as to how this might be implemented would be a new type of URL:
exec://your.machine.here/scriptname --- for remote scripts
exec://scriptname --- for local scripts
This would essentially (but wouldn't have to) do away with the cgi-bin
directory and allow users to place scripts where they liked.
Unforunately this seems to break with convention that a URL type represents
a unique and singular transfer protocol. This implementation would require
"exec" to use http when functioning remotely. Obviously for local scripts,
some shell like functionality would have to be built in to the browsers.
The clear advantage of this is the ability to take entire hierarchies of WWW
server data, cgi-scripts, databases and/or search engines and burn them onto
CD-ROMs (for example) and then access them locally. While the limited
bandwidth of todays networks makes that a useful application now, future
applications might include self contained kiosk units, etc.
I envision mainly two counter arguements.
1) As the bandwidth increases, as it will, there will be no need for
distributing data on fixed media, but instead, everyone will just get what
they want over the network.
RESPONSE: That bandwidth availability is not currently in place, and
probably is far enough away that valuable use will result from this
alternative. Furthermore, there may always be situations where people want
to take data "on the road" with them, perhaps even to places where the
network has not yet reached.
2) Why not write proprietary viewing software for your database or hierarchy
which allows you to run local scripts?
RESPONSE: Building into a URL allow the browser to seemlessly go from the
local machine to the network and back without quitting one application and
starting another. It also allows the same authoring conventions to be used
when constructing the local information so that portability and use by
others is straightforward.
Paul Wilson (608) 265-4573
Trace R&D Center firstname.lastname@example.org