<html>
<head>
<base href="https://wiki.asterisk.org/wiki">
<link rel="stylesheet" href="/wiki/s/en/2171/18/9/_/styles/combined.css?spaceKey=TOP&forWysiwyg=true" type="text/css">
</head>
<body style="background: white;" bgcolor="white" class="email-body">
<div id="pageContent">
<div id="notificationFormat">
<div class="wiki-content">
<div class="email">
<h2><a href="https://wiki.asterisk.org/wiki/display/TOP/Routing+Service+Use+Cases">Routing Service Use Cases</a></h2>
<h4>Comment <b>removed</b> by <a href="https://wiki.asterisk.org/wiki/display/~beagles">Brent Eagles</a>
</h4>
<br/>
<div class="notificationGreySide">
<p>This may or may not be relevant to describing use cases, but I feel the language implies certain functional behaviors and clarification is warranted.</p>
<p>With respect to endpoint registration and validation: if a set of endpoints are part of the registration transaction and there are multiple conflicts do we create multiple exceptions (as indicated) or one exception listing the invalid entries. I would expect the latter. Secondly, is it expected that the valid entries are still stored in the event that an exception is thrown on invalid entries? I'm leery of non-atomic method semantics but perhaps this kind of thing is expected in these types of applications?. Is there a practical use case for accepting part of a set of data? The language around replication isn't very generic with respect to the mechanism of replication. Is that deliberate?</p>
</div>
<div id="commentsSection" class="wiki-content pageSection">
<div style="float: right;" class="grey">
<a href="https://wiki.asterisk.org/wiki/users/removespacenotification.action?spaceKey=TOP">Stop watching space</a>
<span style="padding: 0px 5px;">|</span>
<a href="https://wiki.asterisk.org/wiki/users/editmyemailsettings.action">Change email notification preferences</a>
</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>