On Sat, 2013-12-07 at 08:13 +0100, Richard Cochran wrote: > On Fri, Dec 06, 2013 at 05:11:48PM +0000, Keller, Jacob E wrote: > > > > What do you think about having an extended message which indicates "I am > > ready to receive".. then once ptp4l gets this, it then starts pushing a > > set of notifications on events. > > > > I like this better than a configuration option, since it means ptp4l > > only sends messages on the uds when some management interface has > > requested it... > > > > Thoughts? > > I think this should be "configurable" at run time, *not* as a > configuration file option. I imagine having a custom management > message that allows the client to request different kinds of status > information, like port state, BMC result, and so on. (Or maybe the > client can specify management ID values.) Whenever any of the > "watched" status bits change value, then ptp4l will push RESPONSE > messages as if replying to a GET. > > How does that sound to you? >
That's exactly what I was imagining with my post above. I also dislike the idea of static configured at start. This seems the most useful. How would this work with multiple management interfaces? Is that even possible? IE: multiple programs connected? Does the management interface properly only send to a single client? If so we can use the client-request details to send the data across to only that client. This way only clients which perform the proper request message get the result. Thanks, Jake ------------------------------------------------------------------------------ Sponsored by Intel(R) XDK Develop, test and display web and hybrid apps with a single code base. Download it for free now! http://pubads.g.doubleclick.net/gampad/clk?id=111408631&iu=/4140/ostg.clktrk _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
