....(Public|Private-Client Data)->Master server<-(Recipes 1,2,3,4...)....
......^V......^V.................................. ...........................V............
......^V...<encrypt>.............................. .................<certify>......
.......CD Client<->Master Recipe Sv.|Other Recipe Sv.|Content Sv.

Hi Vick and All,
I liked your diagram and logic. Let's keep looking at all the possibilities.
In addition to serving up certified recipes and client recipes, the klik
server could keep special groups of recipes for the private use of a client.

A private client recipe "PCR" could be as simple as "put my unfinished
term paper on my desktop and configure my word processor the way I
like it". This could be automated and done at boot up.

As I suggested in a previous post, the kilk server would not hold the
actual data -- just recipes to fetch data, configuration files, or
add on programs. The CD Client would have to purchase web space for
his documents.

As a business model, the recipes are a "loss leader". These are best
open source and free. However, free (as in freedom and liberty) does
not have to mean there is no charge for an account for the PCR space.

Best Wishes
paradocs
-------------
Posted in my Grandfathers Saloon in German:
Today for Cash, Tomorrow for Free!