Silicon Investor (SI) -- The First Internet Community

STOCKTALK

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor. We ask that you disable ad blocking while on Silicon Investor in the best interests of our community. If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.

Technology Stocks : Novell (NOVL) dirt cheap, good buy? -- Ignore unavailable to you. Want to Upgrade?

To: PJ Strifas who wrote (34730)	11/8/2000 11:30:19 AM
From: Paul Fiondella	Read Replies (2) \| Respond to of 42771

You are thinking down the right road Peter Now just take everything in that process that can be hidden away from the user as a detail and everything that can simplify the experience --- and put an attractive end user umbrella over the process, and you are getting into your stride. Book it. Bill it. Take it to market.

To: PJ Strifas who wrote (34730)	11/12/2000 12:30:17 PM
From: Scott C. Lemon	Read Replies (1) \| Respond to of 42771

Hello PJ, So I'll add some more information from my architecture that was the original premise of my work on digitalMe ... this is all quite possible ... > Napster uses eDirectory for user authentication and access > priviledges. I register with them and they create an > account for me (called it PJNapster). They use this user > object to grant me priviledges within their system. > (perhaps they can use it for accessing music or managing > certificates too!) So in my world, this is actually part of the "Membership Application" process. As humans in the atomic world, we have this down to a science. So you actually "apply for membership" and they provide you with a "membership ID". This is then your "account" with them. > I have a Personal Directory installed on my PC at home and > created a "myDirectory" that stores my personal data. The > user I created there was PJStrifas. I populate PJStrifas > with personal information (name, address, phone, etc). > When I access my PC, Personal Directory is started and I > log into it using my user name and the password I chose. Yes ... this is where I will accumulate my life information ... all of my personal information. > When I want to access my Napster information - I use > client software (in this example, Novell Client) to log > into their Directory. Since Personal Directory is an open storage platform, and supports open protocols, any application (that "logged in") could access my personal and membership information and objects. > To do this, I "tell" Personal Directory that I'm logging > into a remote Directory and it asks for my crendentials to > do so for me (username & password). Or, in my world, an application does this as a completely automated process ... ;-) > After successful log in, Personal Directory caches ALL > information associated with my user object in Napster's > Tree locally. So this could be done, or during the membership application process we actually negotiate the bi-directional identity exchange policies ... which is how I'm doing it. > So when I look at my Personal Directory, I would see user > entries for PJStrifas and PJNapster (simplified > explaination). In my world, these are two distinct types of objects ... a user object, and a membership object. One is "me" and one is my identity that has been negotiated with a friend or organization. > I can then choose to synchronize information between > PJStrifas and PJNapster. I literally pick and choose what > information I will share with Napster (ie, address, phone > number, etc). Again, in my world, this is negotiated up front, and then can be modified throughout my life, or during the term of the relationship. > At a predefined interval, my Personal Directory will > synchronize the cached information of my Napster user > (PJNapster) back to the Napster Tree. And this can be very easily be event driven ... > So in the end, the information contained in the properties > of my Napster user object are "filled" by the sync process > with my Personal Directory. I control what information > Napster has based on the fact that I fill out the > properties of my user object in their tree! Yep ... Personal control over "selective replication" ... > Now, extending the Directory to store information beyond > the basic user is going to be an interesting development. Actually, in my world, this is very simple ... a natural outgrowth of the system ... > Napster would need to extend the schema (rules defining > objects) to hold whatever information it deems necessary. > In doing so, my local schema would ALSO need to be > extended to be able to identify the extensions otherwise I > could not manage them correctly. Yep ... and so my personal identity will continue to grow throughout my life ... Scott C. Lemon