Object oriented view of the Internet and the World Wide Web

Looking at the Internet and the World Wide Web in the abstract sense of object oriented thinking (OOT), you can visualize the structure of the Web in many different ways; from different view points; with different paradigms.

In this way, you will soon come to realize that the conventional view of the Internet and the World Wide Web is only one of many possible different ways in which the Internet and the Web can be considered.

The usual way of looking at the Web is from the view point of conventional media. It is the paradigm of the source broadcasting out to the recipients; the server Web site offering up its messages to clients; the server source creating packages which the recipient client observes and digests.

This is the normal way of seeing the operation of all conventional media, with the action and the creativity focused at the source of the information. From this particular view point, seeing the Web as consisting of platforms in the sky, beaming down images to the masses below, seems a reasonable analogy.

But is this the best way to view it?

Now, "morph" this vision of the Web to see it from the client side. The client side sees the Web through a portal in a client side computer. As far as the client side computer is concerned there is no great World Wide Web at all: there are only millions of files which are accessible through a telephone link from the desktop.

What gives the illusion, to the observer on the client side of the Web, that the Web is anything other than a collection of computer files is the client's browser application, which creates a fantasy on the screen as a direct result of programming prompts embedded within tags in HTML documents.

Web pages are all HTML text documents, which are brought to life by the coded instructions within their tags. In other words, what the client observer sees on the screen when he or she visits a Web site is not something which exists on the Web site, but, something that is created and packaged within their own computer by their browser application which is directed by minimalist prompts from the Web.

How many different ways can you visualize the working of the Web?

One paradigm might see the client computer as constructing images in an allocated memory space according to directions and templates supplied from the Web via a telephone link. You can visualize the whole of the World Wide Web as being on call to create these images.

A morph of the paradigm might visualize the whole of the World Wide Web as being effectively located on the client's hard disc. Millions upon millions of tagged HTML documents instantly and personally available at the client's request.

Now put yourself in the position of the client. How would you, as the client, decide which of those millions of documents to look at?

Can you see what happens to Web sites in this way of looking at things? They all become collections of individual text documents, immersed in a vast sea of similar documents, struggling to survive by trying to attract the client's attention and be called upon to prompt the same browser application. What can any of them possibly do to get the client's attention?

From this way of looking at things, you can easily see that the only certain strategy for any particular site owner to get a client's attention is through sending suitable instructions to the client's browser. In other words, think about the client's view of the web - not your projections from it

If you belong to any of the Internet marketing groups you will have noticed how scornful experienced Internet marketeers are of the efforts made by many of the top marketing and advertising companies who are coming onto the Web.

These companies have developed their skills and experience in conventional media. Even some of the top names in marketing and advertising are using adaptations of material used in conventional media to advertise and promote their customer's products and services. They seem completely oblivious of the client side view and the part the client's computer can play in the viewing experience; they design their Web sites as if they were pages in a magazine.

Communicating using client side orientation is completely opposite to the way all other media are viewed as working, where the media systems are seen in terms of a central, information packaging organization broadcasting out packaged information to a receptive audience.

The view taken from analogies with a biological system would see the creation and packaging of the information occurring at the receiver end (client). The broadcaster would be seen as a triggering mechanism, sending messages to primed targets (as explained in HGMG - cells, as clients within the human body, receive molecular messages which are acted upon by the cell to produce products specified by the message).

Because this is such a radically different concept from the way all other media are viewed as working it may explain why the conventional marketing and advertising firms have had such poor results from the Web so far.

Client Oriented Intranet Systems (COISes)

On first thoughts, it would seem to be a silly strategy for a Web site owner to try to get a client to use a browser which is custom made only for their own particular Web pages. Why should a client want to bother with a browser that works only on one particular site? Surely, clients will prefer browsers that can get information from as many sites as possible?

But is this true? For general browsing maybe, but, supposing a client just wants a fast and efficient route to some specific data or info. Supposing the client wants a particular convenient and intelligent service, or, help in deciding between a range of products?

In these circumstances, wouldn't the client prefer a button on the screen that he or she just clicks upon to be able to be transported to exactly the scenario required - without having to do a lot of browser navigations?

If you sell widgets, you want to attract people to your site who are interested in widgets. People interested in widgets would probably be quite interested in having a button which they can click upon to find out all the up to date information about widgets.

How do people get hold of a button that takes them to the widget site? The same way they would find out about how to find a widget site in the first place because the browser button could be downloadable from a regular Web page at the widget site.

The initial reaction, might be to ask why a person should bother to download a button to take them to a Web site about widgets when they are already at a Web site about widgets? This in where a paradigm shift is required which illustrates the difference between traditional media and the Web.

The point of getting a client to download a special button is because that button is more than just a regular browser; it is an intelligent agent; it is a custom browser specially designed for people who are interested in widgets: it is a client oriented intranet system (COIS).

Such a button could include a multimedia shell, a Web buggy, which could present a product or service in the best possible way for both the client and the Web site owner.

If all the visiting clients are using such a particular custom browser, the Web site proprietor can design the Web site to fully utilize all the tricks and techniques available to that browser. If the browser happens to include a player for multimedia documents, all the facilities of multimedia will be available to the Web site designer.

A site need not have to be designed to cater for the lowest common denominator. There would be no need to be concerned with whether or not the client has this plug-in or that particular version of browser or helper application.

In other words, with clients using a custom browser, there will not be a need to design a Web site which will have to appeal to every browser which happens to stumble across the Web site.

And there is no need to worry about browsers recognizing programming instructions, the browser application can be utilized to the limit of its capabilities. If that browser is a Macromedia Director shell for instance, all the full power of multimedia will be available to display and present products or services in full multimedia.

In other words, what you are setting up if you get clients to use your browser, is an Intranet: a private section of Web space in which you can do wonderful things exclusively for the people to whom you have given (or sold) your browser to - your customers, clients, group, friends, colleagues, customers. Who else is there you would want to see your site anyway?

The choice is simple: either you design a Web site to appeal to the lowest common denominator of a mass market and compete against thousands of other sites for attention, or, you design your Web site to optimally please a specially selected group of people who will benefit from what you have to offer. For the first choice you must think "server oriented", for the second you must think "client oriented".

With server side orientation, multimedia can be used to a limited extent but must be confined to plug-in modules which work through general purpose browsers. This greatly restricts the full scope of full multimedia as it has to share control of the space with the browser and be subservient to it and its security specifications.

Once you focus upon a client side oriented intranet solution you have no restraints at all as to how you present your Web site to a client. You are free to use every trick available to the multimedia authoring package you choose to use.

More than one way to skin a cat


When you switch paradigms to view the Internet in terms of Intranets, remember this is only one of several possible mind sets. Sometimes it it far more convenient to see the Net in conventional terms and, as you will see later, Web sites can be turned into Web site objects which turn all what you have just read completely on its head.

[Index]
[Next - The illusions of bots and COISes]
[Back - Intranet - An OO definition]


Peter Small August 1996

Email: peter@petersmall.com

Version 1.00

©Copyright 1996 Peter Small