| 01:27.16 | b3nt_pin | fwiw: the service name mostly affects things like the names of object adapters (still not awesome for dynamic deployment), not the object id's themselves |
| 01:29.20 | b3nt_pin | at the moment, some of the "main/well-known" objects have configurable identities while objects that are created "on the fly" like bridges, sessions, session endpoints, etc. etc. all have dynamically generated object identities. Usually this is a bare stringified UUID or a UUID string concatenated onto some "meaningful" string to help identify the object in question in logging, etc |
| 01:30.50 | b3nt_pin | service name "collisions" in a system may or may not in duplicate adapter ids, which while suboptimal, will not have the same impact as it would if you were using say.. indirect references and IceGrid. |
| 01:32.26 | b3nt_pin | s/may not/may not result/ |
| 01:35.41 | *** join/#asterisk-scf-dev b3ntpin_tm2 (~b3ntpin@142.162.76.111) |
| 02:49.04 | ben2011 | Thank you for clarifying this |
| 04:02.32 | *** join/#asterisk-scf-dev DocAwesome (~DocAwesom@asterisk/documenteur-extraordinaire/blitzrage) |
| 11:18.49 | *** join/#asterisk-scf-dev b3ntpin_tm2 (~b3ntpin@142.162.76.111) |
| 13:56.17 | *** join/#asterisk-scf-dev kpfleming (~kpfleming@asterisk/digium-director-of-software-tech/kpfleming) |
| 14:28.29 | *** join/#asterisk-scf-dev dms1 (~dms@user-69-1-24-49.knology.net) |
| 16:41.22 | *** join/#asterisk-scf-dev b3ntpin_tm2 (~b3ntpin@142.162.76.111) |
| 20:02.00 | *** join/#asterisk-scf-dev dms1 (~dms@user-69-1-24-49.knology.net) |
| 20:13.55 | *** join/#asterisk-scf-dev b3ntpin_tm2 (~b3ntpin@142.162.76.111) |
| 20:53.24 | *** join/#asterisk-scf-dev dms1 (~dms@user-69-1-24-49.knology.net) |
| 23:32.17 | *** join/#asterisk-scf-dev joat (~joat@ip70-160-216-251.hr.hr.cox.net) |