[liberty-dev] ResourceID Question

To <liberty-dev@emailprotection.org>
From “Start Jen” <JEN@novell.com>
Date Thu, 23 Oct 2003 17:00:44 -0600
Reply-to liberty-dev@emailprotection.org
Sender liberty-dev-owner@emailprotection.org

The Discovery specification defines a ResourceID element that the Discovery, Personal Profile, and Employee Profile Services use. I have some questions about the format of the ResourceID.
From what I understand, the following is true:
The format of the ResourceID is specific to the implementation of the service.
The web service “registers” ServiceTypes and ResourceIDs with the Discovery Service.
A “client” will never have to create a ResourceID, it gets them from the Discovery Service. (as per the Discovery spec)
So, now some questions…
1) Does the Personal Profile Service have to register a unique ResourceID for every user record in its database?  What if there are 500M users?
In the Personal Profile service, it appears that a “record” is a given user’s personal profile.  When a <query> is made to the personal profile service, the only way the service will know which user record to access is by using the ResourceID.
2) Given an SP that wants to access the Personal Profile Service, that SP makes a discovery lookup call to a Discovery Service.   In that lookup XML there is a ResourceID element. This SP probably only has a username or pseudonym for the current user. How does the SP tell the Discovery Service which user it wants to locate the Personal Profile service for? There must be some mapping from username/pseudonym to ResourceID? The specs claim that a client will never have to create a ResourceID, so the ResourceID sent in the Discovery Service lookup must be different from the ResourceID returned in the ResourceOffering…. right?
I think I am missing some fundamental link….. and I would appreciate anyone’s help to clarify.
Start Jen

Partial thread listing:

[liberty-dev] ResourceID Question
(Stuart Jensen)
 Conor P. Cahill (10/24/2003)
 Jonathan Sergent (10/24/2003)
 Jonathan Sergent (10/24/2003)
John Kemp (10/24/2003)


Please enter your comment!
Please enter your name here