[Bug 243916] [NEW PORT] misc/biblesync: Multicast shared co-navigation library for Bible programs

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=243916

            Bug ID: 243916
           Summary: [NEW PORT] misc/biblesync: Multicast shared
                    co-navigation library for Bible programs
           Product: Ports & Packages
           Version: Latest
          Hardware: Any
               URL: https://github.com/karlkleinpaste/biblesync
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: ports-bugs at FreeBSD.org
          Reporter: salvadore at freebsd.org
 Attachment #211399 maintainer-approval+
             Flags:

Created attachment 211399
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=211399&action=edit
biblesync port creation

Tested successfully with poudriere on {11.3,12.1}-RELEASE {i386,amd64}.

-------------------------------------------------------
This is a C++ single class library encapsulating a protocol conduit.  The
premise is that there is a local network over which to multicast Bible
navigation, and someone, possibly several someones, will transmit, and others
will receive.  The choices for when you decide to xmit and what to do when you
recv are up to you as the application designer.

Access to the conduit is by creating the object, setting the mode, calling
Transmit() to xmit nav events, and arranging the frequent polling of Receive()
to recv nav events.  There is more than just navigation to be handled; there
are live/dead events for potential Speakers as well as mismatches, presence
announcements, and errors.  There is a programming reference biblesync.7 which
explains the details, both from a high level view of the essentials of the
protocol's behavior and at a low level of how you create, access, and use the
conduit class.  The (single) BibleSync object should persist throughout the
life of your application, but at any time you can set the mode to "disable,"
and preferably stop the receive polling, and then re-enable it later as the
user needs.
-------------------------------------------------------

-- 
You are receiving this mail because:
You are the assignee for the bug.