okay, i like the 'usrloc-ng' approach. Will see what we can do.<div><br></div><div>Cheers</div><div>Jason<br><br><div class="gmail_quote">On Wed, Feb 1, 2012 at 1:04 PM, Daniel-Constantin Mierla <span dir="ltr"><<a href="mailto:miconda@gmail.com">miconda@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<div><div class="h5"><br>
<br>
On 2/1/12 11:50 AM, Jason Penton wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Daniel, you will probably be most interested in this based on yesterday's dev chat....<br>
<br>
Following the discussion from the dev irc yesterday re. usrloc requirements:<br>
<br>
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?<br>
<br>
I'd be interested in yours/other interested members' input.<br>
</blockquote></div></div>
I haven't looked at specific implementations, just some overview to see what missing features are in one or the other. I think k version of usrloc/registrar pair has more on db modes and record matching (call-id, etc...), branch flags, callbacks for pua_usrloc, $ulc(...) pseduo-variable class. s version has a uid, per contact attributes, sip-instance support and implements DB2 API which unfortunately not implemented across all db connectors, thus limiting the backends. So the merge should preserve the functionalities from both, looks like going to be a bit of effort to do it. If you want to start, I may help, eventually contributing some parts or during the design process. Starting from one or the other, is a matter of developer preference -- can be started from scratch, like usrloc-ng :-), taking from each of existing "only the good parts".<br>
<br>
Cheers,<br>
Daniel<span class="HOEnZb"><font color="#888888"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
-- <br>
Daniel-Constantin Mierla -- <a href="http://www.asipto.com" target="_blank">http://www.asipto.com</a><br>
<a href="http://linkedin.com/in/miconda" target="_blank">http://linkedin.com/in/miconda</a> -- <a href="http://twitter.com/miconda" target="_blank">http://twitter.com/miconda</a><br>
</blockquote>
</font></span></blockquote></div><br></div>