Frames and IFrames

Using frames and iframes to support web 3.0 pages is a great way to simplify the architecture, and avoid the complexity of AJAX. It also makes implementation of a CDN easier.

There are many ways to provide graceful search engine indexing of the pages - using Google’s site maps, Apache rewrite rules, and other creative approaches. Imagine the rich pages you could build, easily. Augment it with sophisticated browser caching and you can greatly speed the pages and reduce bandwidth requirements.

This also supports the idea of micro pages mentioned earlier.



LAMP is all about layers. Passing data from a database up to a client. Each layer is responsible for translating the data from its source, to be ready for its destination.

Thus, if the database architecture is less than ideal, it should be masked by the PHP - so the javascript and HTML are not affected. That way, when improvements are made, the upper layers still work.

This is similar to the ISO model. Or is that OSI? The 7 layers (which may not be correct).


You may say Linux and Apache are layers 1-3
PHP could be layers 4-6
MySQL could be layers 2 and 3
HTML/javascript could be layer 7

The Value of Web 3.0

The value of web 3.0 will be in its content, not in the technology to deliver it. To succeed, a company must make extremely efficient use of techonology for delivery, and focus on valuable content resources (people).

As with everything, the web is becoming increasingly specialized. Pure social networks that are intended to serve as resources will be replaced by managed content systems where the bulk of the material is posted by professionals and site visitors will offer supplementary content.

There are great opportunities for building sites of user contributed content, but the users should be qualified, and they should be rewarded with some benefit. An example would be a teachers’ system. Teachers (who are intelligent, resourceful, and creative) can share materials with other professionals in the education field. Their contributions can be rated, and those ratings can be used to offer items of value. For example, gift cards to stores that offer products they may appreciate - either personal or professional. In this case, the producers and consumers are from the same population. Another module could be to have medical professionals offer content for the general public. These are just examples.

The platforms these are built on must be extremely robust. The software itself is actually of limited value - it is only important to deliver the content, but that content must be protected, and preserved. This requires a careful storage architecture that should be portable.

Micro Pages for Web 3.0 ?

More web 3.0 ideas

  • Build pages as collections of frames or iframes
  • Construct alternate access for pages to allow subsections to be delivered. This means a page could have a ‘full’ mode, or a ‘piece’ mode. ‘Full’ mode would deliver the entire page, ‘piece’ mode would deliver a designated piece of the page.
  • Use AJAX (with care), or dojo widgets (with care!)
  • Look into Google gadgets (I confess I haven’t done this yet)

Web 3.0 Implementation Ideas

This are very rough ideas.

Imagine requesting a page, identifying the start and end of the parts you are interested in, setting the BASE tag as appropriate, and leaving the contents of the HEAD section. That may deliver a functional page segment.

The idea is to pull in content from a page, that may not be constructed to deliver its content in segments. In other words, a traditional web page, intended to function as a unit - not a collection of elements.

Later refinements could filter unused elements to reduce the bandwidth requirements.