Things which exist on one's personal computer are referred to as "client side", and on the web host as "server side". The average internet user might have first heard "client" in the context of applications installed on the personal computer, such as "email client". Those mail systems which can be used from anywhere are "web mail", and exist on the server side.

In practical terms, all your office suite programs, media players, programs to edit images, most games, and so forth, are probably client side, although "utility" type functions are evolving on the server side. For example, users can now share data on server side spreadsheets and word processors.

Most browser function is defined on the client side, perhaps with some JavaScript add-ons for interaction, calendars, multi-level menus, animated graphics, et cetera.

Business enterprise level content management, databases, store systems, and much more are on the server side. Server side programming can range from simple CGI scripts ("Common Gateway Interface") written in a variety of languages, such as Perl. Large databases can be built in the popular open-source MySQL, and accessed through interfaces programmed in PHP.

First embodiments of such CGI functions started a new copy of the executing module for each command request. To avoid server shutdown from excessive workload, host programmers have evolved better ways, but these need not concern us ordinary mortals.

Fortunately for this author, a web site builder does not need to be an expert in all those server side tools in order to use them. Most hosting companies now offer access to pre-installed modules. Persons wanting better features can purchase modules from third parties to upload and install, such as shopping carts, which are backed by support staff, user, or similar.

If the site builder lacks a very fast connection to the server, s/he can install client side copies of operating systems for SQL, PHP, other... to emulate behavior on the host. Sometimes the emulation is less than perfect, such as with different release generations, so adjustments may be needed after upload.

Why would anyone bother to do this? One reason is that PHP can take over parts of HTML coding, such as with "include files" which represent often used sections of header, footer, body, or serve more robustly than JavaScript for interactivity and utility functions.

If the connection is fast, however, present day "shared hosting" and "virtual private/dedicated servers" make it very difficult for one domain owner to break the system for other users. And only privileged employees have access to the power switch. VPS allows power users to get more behind the scenes than can the SH customer.

Caveat: Whether your HTML writing is done directly on host account or on personal computer for upload, keep an off-site copy against the day your hosting company drops or back levels your content. It will happen.

What ever the approach a person uses for working on the internet, all these elements are examples of "distributed processing", a concept which some large mainframe computer manufacturers had hoped would never be realized. Now that the small guys and gals have forced the issue, by using ever more powerful personal computers in place of dumb terminals, the big dogs have learned to love and profit from it.

Last February, I received a call from a man in Wisconsin asking about my writing services. He was particularly interested in having me rewrite the copy on his Web site. I was very surprised and wondering how in the heck he got my name. Then he mentioned something about my being my Internet hosting service's "customer of the month." I was very pleasantly surprised. After I spoke with him, I logged onto my email and there was an e-newsletter from my host server. And, yes, I was the "customer of the month," and my Web site was the featured site for the month.

Of course, I quickly hastened to my site and checked the traffic. I was up to over 300 visits to my home page for the morning, and the day was to end with 796 visits! I don't believe I'll ever see numbers like that again. I also received several other calls from people interested in my services.

It wasn't a complete surprise that my site was featured. Last year, I had filled out a "success story" response form on the company's site. I was later interviewed and told that I would be used as a case study. But the case study never materialized so I had forgotten about it. Thus I was very pleased when my site landed in their e-newsletter as the featured site.

My host is one of many companies where you can register domain names and get your business online. They will build a site for you; or, if you are cheap like me, you can build your own.

When I began my business a few years ago, I waited a whole year for my brother who owns an ad agency in L.A. to professionally build my Web site for free. Now he's kind of successful, and he didn't get that way by doing a lot of free work for relatives. At the time, my server was doing a lot of radio advertising claiming you could "build your Web site in 20 minutes." One day after nagging my brother once more, he became exasperated and said, "Why don't you just build your own."

So I did. I called the company and they provided templates and lots of help. I chose an animated template with a layout ideal for showcasing a portfolio. There was a bit of a learning curve. I had to play around and call for help a few times. It took me longer than 20 minutes; yet, technically, the commercial was accurate: you could really get a home page up with your contact info in 20 minutes. I believe I spent about 20 hours to get my Web site to the point where I was willing to "publish" it.

One of the advantages I have found about building your own Web site is that you don't have to rely on an outside Web Master to update it. Sometimes those fellows are swamped and it can take awhile. If I want to put a new project in my online portfolio, I can do it in a few minutes. Or if I want to add something new to my list of services, I can quickly type it in and it's done.

I found a huge difference in how I was perceived in the business community once I had a Web presence. Suddenly, I was taken seriously. These days when someone asks, "What's your Web address?" you should have it ready. And it should never be "under construction." Visitors find that very irritating. It's really not that hard to get a presentable Web site up.

As I mentioned earlier, there are numerous places where you can go to build a Web site. Just Google "do it yourself Web site" and you will get numerous options.

It is very inexpensive. My site costs me less than $100 a year for 20 pages. Some places are even cheaper. Compared to the thousands of dollars one can pay a Web designer, it's a sweet deal.

That's not to say that I don't believe in professionally designed Web sites. I still want one with more bells and whistles. I'm just waiting on my brother.

(Since initially writing this piece, my server has made the process even better. It's more professional, a lot more pages available ... and more bells and whistles.)

Like a lot of web developers, I'm not always that disciplined when it comes to the file naming convention I use and I sometimes end up with a situation whereby I have some files that are in lowercase, some that begin with a capital, and some that are a bit of a mixture.

One web site I maintain contains about 2000 web pages and has about 20,000 hyperlinks. As you can imagine, I had one of those sinking feelings when I was told that in order to migrate the web site to a new content management system, all the file names and hyperlinks would need to be changed to lowercase.

Whenever I am presented with a problem like this, my instinct is always to write a Perl script using one or more regular expressions to solve the problem. This particular situation was no exception.

Change a string to lowercase

The following regular expression changes all the characters in a string to lowercase. The first part of the regular expression finds a hyperlink, and the second part converts the string. (Just in case this article is not displayed correctly, there should be a single backslash in front of the 'L$1').

Change a filename to lowercase

Likewise, changing a filename itself is very simple. The following two lines perform the task quite nicely:

(Again, there should be a single backslash in front of the 'L$name'.)

If you need more information on how to incorporate the above code snippets into a complete script, feel free to contact me directly.