[sr-dev] K|S usrloc merge

Daniel, you will probably be most interested in this based on yesterday's dev chat.... Following the discussion from the dev irc yesterday re. usrloc requirements: To summarise the functionality required for GRUU - unique id (for you) and custom subscriber data (for us). As you mentioned yesterday, S version of usrloc has this particular functionality. After a brief look at S-version of usrloc this morning, I have to say I prefer it. Mainly because of the way it handles urecords and ucontacts separately. In K-version - a urecord structure really only exists if there is a contact. There are more deadly implications when in DB mode where a static urecord structure is built on demand. IMHO, I think we should use S module as the basis of a merge? I'd be interested in yours/other interested members' input. Cheers Jason