<div dir="auto">So, for the past couple of days the SurveyMonkey results are not changing, with 13 replies overall. Should we wait for more or everyone passionate enough has already spoken? In practice I'd likely follow up on a weekend anyway, but... the weekend is coming! :)<div dir="auto"><br></div><div dir="auto">Currently we have a clear leader pair that collected almost half the votes (6), two votes were to keep old words in place - alas, nowadays doing nothing (and breaking nothing) does not seem to be a viable option.</div><div dir="auto"><br></div><div dir="auto">Also reminding that there are PRs open for the docs/comments changes, some closely related to this subject (#992 along with code) and some bystanders that "fell under a hot hand" (#989, 990, 991) - feel free to review the proposals if they make sense or should be improved ;)</div><div dir="auto"><br></div><div dir="auto">Thanks to all,</div><div dir="auto">Jim</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Mar 13, 2021, 13:41 Jim Klimov <<a href="mailto:jimklimov%2Bnut@gmail.com">jimklimov+nut@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Thank you for the suggestions, keep them coming :)<div dir="auto"><br></div><div dir="auto">To me, I think I considered pub-sub but it did not quite fit - gotta refresh my memory by code re-reading (or expert comments) - I found I'm vague now on who hits the big red button to shout that a particular power source device got critical - the upsmon in "master" role, or "upsd" that talks to all subscribed (indeed!) upsmon's and just some choose to stop asap (if they won't have enough PSUs powered) and others wait for them to pull the plug on UPS afterwards :)</div><div dir="auto"><br></div><div dir="auto">So if in a way upsd is a message broker between many clients actively emitting commands, pub-sub is an option. If upsd emits messages differently based on roles of registered clients - not so much.</div><div dir="auto"><br></div><div dir="auto">Note also that there technically can be multiple machines with connections and ability to bring the UPS down (or several UPSes) and perhaps configured so for redundancy, so in general case it is neither a 1:1 nor 1:many relationship.</div><div dir="auto"><br></div><div dir="auto">Jim</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, Mar 13, 2021, 05:05 Douglas Parsons <<a href="mailto:doug@parsonsemail.com" target="_blank" rel="noreferrer">doug@parsonsemail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>There is, </div><div dir="auto"><br></div><div dir="auto"><a href="https://en.m.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern" rel="noreferrer noreferrer" target="_blank">https://en.m.wikipedia.org/wiki/Publish%E2%80%93subscribe_pattern</a><div dir="auto"><br></div><div dir="auto">I said I stayed away from it because of the Cisco link. Others as well as you are free to persue it. I was just making suggestions.</div><div dir="auto"><br></div><div dir="auto"><br></div><br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Fri, Mar 12, 2021, 10:43 PM Baker, Lawrence M <<a href="mailto:baker@usgs.gov" rel="noreferrer noreferrer" target="_blank">baker@usgs.gov</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;line-break:after-white-space">
<div style="word-wrap:break-word;line-break:after-white-space">
That is terminology from Computer Science. (Decades ago?) It is familiar. Not invented by Cisco. As in, producer-consumer, from the same time. Those were all different paradigms for client-server relationships. There must be Wikipedia citations that can
be consulted. As I recall, there were distinctions, such as, producer-consumer were tightly bound, where the producer had no purpose without a consumer. In publisher-subscriber, subscribers registered their interest in what the publisher had to say, but
were neither required to exist at all, or might ignore what was being published.<br>
<div><br>
</div>
<div><span style="border-collapse:separate;color:rgb(0,0,0);font-family:'Helvetica Neue';font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">Larry
Baker<br>
US Geological Survey<br>
650-329-5608<br>
<a href="mailto:baker@usgs.gov" rel="noreferrer noreferrer noreferrer" target="_blank">baker@usgs.gov</a><br>
<br>
<br>
</span></div>
<div><br>
<blockquote type="cite">
<div>On Mar 12 2021, at 7:22:35 PM, Douglas Parsons <<a href="mailto:doug@parsonsemail.com" rel="noreferrer noreferrer noreferrer" target="_blank">doug@parsonsemail.com</a>> wrote:</div>
<br>
<div>
<div dir="auto">I didn't go there due to its use by Cisco.</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Mar 12, 2021, 10:03 PM Baker, Lawrence M via Nut-upsuser <<a href="mailto:nut-upsuser@alioth-lists.debian.net" rel="noreferrer noreferrer noreferrer" target="_blank">nut-upsuser@alioth-lists.debian.net</a>> wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;line-break:after-white-space">
<div style="word-wrap:break-word;line-break:after-white-space">
<div>Jim,</div>
<div><br>
</div>
The terminology I recall for that one-to-many relationship is publisher-subscriber.
<div><br>
<div><span style="border-collapse:separate;font-family:"Helvetica Neue";font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-variant-east-asian:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:-webkit-auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px">Larry
Baker<br>
US Geological Survey<br>
650-329-5608<br>
<a href="mailto:baker@usgs.gov" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">baker@usgs.gov</a><br>
<br>
<br>
</span></div>
<div><br>
<blockquote type="cite">
<div>On Mar 12 2021, at 6:24:38 PM, Phil Stracchino via Nut-upsuser <<a href="mailto:nut-upsuser@alioth-lists.debian.net" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">nut-upsuser@alioth-lists.debian.net</a>> wrote:</div>
<br>
<div>
<div><br>
<br>
This email has been received from outside of DOI - Use caution before clicking on links, opening attachments, or responding.<br>
<br>
<br>
<br>
On 3/12/21 9:14 PM, Rusty Bower wrote:<br>
<blockquote type="cite">Manager/subscriber seems most accurate<br>
<br>
Sent from my iPhone<br>
<br>
<blockquote type="cite">On Mar 12, 2021, at 20:13, Douglas Parsons <<a href="mailto:doug@parsonsemail.com" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">doug@parsonsemail.com</a>> wrote:<br>
<br>
<br>
In place of secondary how about subscriber? It would be accurate to<br>
the role.<br>
</blockquote>
</blockquote>
<br>
<br>
I'd been going to suggest controller and ... something. Controller and<br>
subscriber?<br>
<br>
<br>
--<br>
Phil Stracchino<br>
Babylon Communications<br>
<a href="mailto:phils@caerllewys.net" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">phils@caerllewys.net</a><br>
<a href="mailto:phil@co.ordinate.org" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">phil@co.ordinate.org</a><br>
Landline: +1.603.293.8485<br>
Mobile: +1.603.998.6958<br>
<br>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">Nut-upsuser@alioth-lists.debian.net</a><br>
<a href="https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Falioth-lists.debian.net%2Fcgi-bin%2Fmailman%2Flistinfo%2Fnut-upsuser&data=04%7C01%7Cbaker%40usgs.gov%7Cb01ce3a796ae4eac503b08d8e5cf4b28%7C0693b5ba4b184d7b9341f32f400a5494%7C0%7C0%7C637512025774162066%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=BUrriooegO%2BufxvgamwuSSYbbACoc4R5Bn4W2N7qaFs%3D&reserved=0" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Falioth-lists.debian.net%2Fcgi-bin%2Fmailman%2Flistinfo%2Fnut-upsuser&data=04%7C01%7Cbaker%40usgs.gov%7C02f93786357b4c8628c808d8e5c99173%7C0693b5ba4b184d7b9341f32f400a5494%7C0%7C0%7C637512001184607208%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=aR0FjsOcr6yUjWZzRIKVSLlhF%2BDXVn%2F84CZ4%2Br3Dvqo%3D&reserved=0</a><br>
</div>
</div>
</blockquote>
</div>
</div>
</div>
<br>
</div>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net" rel="noreferrer noreferrer noreferrer noreferrer" target="_blank">Nut-upsuser@alioth-lists.debian.net</a><br>
<a href="https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Falioth-lists.debian.net%2Fcgi-bin%2Fmailman%2Flistinfo%2Fnut-upsuser&data=04%7C01%7Cbaker%40usgs.gov%7Cb01ce3a796ae4eac503b08d8e5cf4b28%7C0693b5ba4b184d7b9341f32f400a5494%7C0%7C0%7C637512025774162066%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C2000&sdata=BUrriooegO%2BufxvgamwuSSYbbACoc4R5Bn4W2N7qaFs%3D&reserved=0" rel="noreferrer noreferrer noreferrer noreferrer noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
<br>
</div>
</blockquote></div></div></div>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net" rel="noreferrer noreferrer" target="_blank">Nut-upsuser@alioth-lists.debian.net</a><br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer noreferrer noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</blockquote></div>
</blockquote></div>