It all sounds sensible to me. But you say you don't
need a website. Anything else would seem unprofessional.
I wouldn't think much of a company that gives me links
to tutorials on youtube, dropbox, idrive, or whatever.
(On the other hand, I do know people who have switched
their email from
in...@theircomany.com to
theirc...@gmail.com.... Can't get much more tacky
than that. :)
I think the website approach would be good with one
caveat: The videos shouldn't be too big. You'll have a
generous traffic limit, but it's still a limit.
With a website you could also provide online help pages
that people could visit. You might even make a login page
for people to download videos directly. (I've never done
that, but it shouldn't be hard. Web hosts come with all
sorts of plugins. And PHP samples are freely available for
Unix/Linux servers. You can get on a Windows server, but
personally I prefer Unix. Despite being experienced with
VBScript I found ASP to be more than I wanted to deal
with. It's a closed community dealing with proprietary
tools, while Apache on Unix runs the rest of the world and
lots of people have provided free docs, scripts and plugins
for it.)
So... OK... you get a domain and a host. In 2-3 days the
DNS system will update with your domain and
www.ivar.com
will go to your index page. (You don't have to build a website
if you don't want to. You could just put up index.html and
put the text "
www.ivar.com" on that. That would basically
serve as no website but provide a polite Web version of
"sorry wrong number".) Then you need an FTP program,
like Filezilla. It's as easy as Explorer. You log in to the server
and see your site, which is just a subfolder on an Internet-
connected computer. (I use it daily to download and read my
server logs. In fact, it's so simple that many WYSIWYG web
design programs, for people who don't understand any of this,
claim to provide "editing on the server". All they're doing is
FTP-ing the latest update with each file save.)
Your index page goes in the top level
folder. You can create any number of subfolders and pages.
I like to keep all pages and .css files in one place and put
extra files, like images and zips, in their own folders.
Some big commercial companies actually have a folder for
each page, but I suspect that's due to automation.
Increasingly, corporate webpages are just javascript
"applets" served from a database. In any case, you can
organize things however you like, as long as you keep
your URLs straight when giving them to customers.
For the sake of organization you might want to create a
"video" folder and an "update" folder. Then people get your
videos from
www.ivar.com/video/ and they download the
2 KB file from
www.ivar.com/update/. With a 2 KB update
file there's no point even checking the date on the file.
Just download it, and design the update file to have a
version number in the first line.
Also, create a robots.txt file in your top-level public
folder, where index.html is. In that file put the following:
User-agent: *
Disallow: /video/
Disallow: /update/
That will cause all search engine bots that respect robots.txt
to not list the content of those folders, so that you're videos
don't end up on Google.
Also in the subfolders, put an index.html file with nothing
but a META refresh tag, so that casual visitors cannot see
a listing of the file content of the folder.
You can also create .htaccess options if you're on Unix.
Each folder can have a .htaccess file that applies to all
sub-content. For instance, you could cause all visitors to
get a 403 access denied page when visiting /videos/ unless
they come from one or more specific IP addresses, or if
they do come from a given address.
Lots of things are possible, but the gist of it is that
a website is no more than a public PC that allows file
sharing. The difference is that it's online and there's a
system in place for people to find the IP address of your
site by typing
ivar.com into a browser.
news:1FfEs.798635$g62.3...@fx06.am4...