OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrp-wsia message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Subject: [wsrp-wsia] Create Issue: profileKey scope



Topic:  user info
Class:  Technical
Title:  Should profileKey be persistent?
Document Section: 4.1.2
Description:
In section 4.1.2 (page 21 in 0.7), it says:
"profileKey: A string that MAY be used as a reference to the UserProfile and that MUST remain invariant for the duration of a Consumer's registration"
This insinuates that the profile can be persisted at the producer, and this is the key to that data. On the other hand there is no way to destroy this persistence in the spec.
I don't think there was any intention to require the consumer to send a persistent user ID to the producer. I can see why it is important in the context of a session, but especially since a different entity is cloned for each user, this seems unreasonable, and an invitation for abuse by producer
developers.



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [Elist Home]


Powered by eList eXpress LLC