Thanks for the pointer, I had not looked at those fields in Container yet - I can see that there were grand plans indeed, what I don't see is where they were supposed to go.
And I mean that in many ways. It's not clear where each one of these services was supposed to be implemented, how they were supposed to be integrated with the rest (.ini file or some new mechanism) and finally - I'm not entirely sure what problems some of them were supposed to solve. For instance status.config - if that had a fixed (configurable in some way) port the service_announcement you pointed to would make sense and be quite useful. Can you elaborate what you meant by different transports? What is it you are looking for? Have fun, Markus On Mon, 27 May 2019 17:35:00 +0200 (CEST) <[email protected]> wrote: > 27. 5. 2019 3:20 od [email protected]: > > > In my quest to figure out how machinetalk works I came across the > > following in mkwrapper.py: > > > > def main(): > > parser = argparse.ArgumentParser( > > description='Mkwrapper is wrapper around the linuxcnc > > python module' 'as temporary workaround for Machinetalk based user > > interfaces' ) > > So if mkwrapper.py is/was considered a temporary workaround, how > > does/should the real thing look like? > > > > Problem with Machinetalk, one which needs to be remembered at all > times, is that it is in an unfinished state from a development point > of view and probably the specification was never finished also. Hard > to say as Michael Haberler, who cooked it up at the beginning, left > the project and I don't know if Alexander Roessler is active in > Machinetalk development anymore. > > So short term band-aids become long term solutions. Not good but > probably good enough for now. > > As you can see the Machinetalk suffers a little bit by grandiose > dreams which never materialized. Like the preparation work in > Container > message, > https://github.com/machinekit/machinetalk-protobuf/blob/master/src/machinetalk/protobuf/message.proto#L128 > <https://github.com/machinekit/machinetalk-protobuf/blob/master/src/machinetalk/protobuf/message.proto#L128> > , > for ZeroMQ thought up service discovery instead of DNS-SD/mDNS. Also, > it didn't cover the problem of multiple transport protocols > (IPC/TCP/UDP), which I think is sorely needed. And the NOTYET defines > are still open work in the source code. From today point of view, I > think it needs some rework. And I am open to discussion on how to do > this. (I am of the opinion that the definition should be accessible > before the code.) > > Cern. > > > > > > > > -- > > website: > http://www.machinekit.io <http://www.machinekit.io>> > > blog: > http://blog.machinekit.io <http://blog.machinekit.io>> > > github: > https://github.com/machinekit > > <https://github.com/machinekit> --- You received this message > > because you are subscribed to the Google Groups "Machinekit" group. > > To unsubscribe from this group and stop receiving emails from it, > > send an email to > [email protected] > > <mailto:[email protected]>> . Visit this > > group at > https://groups.google.com/group/machinekit > > <https://groups.google.com/group/machinekit>> . To view this > > discussion on the web visit > > > https://groups.google.com/d/msgid/machinekit/6b0977ef-1595-4919-ae1b-faf3b8428670%40googlegroups.com > > <https://groups.google.com/d/msgid/machinekit/6b0977ef-1595-4919-ae1b-faf3b8428670%40googlegroups.com?utm_medium=email&utm_source=footer>> > > . > > For more options, visit > https://groups.google.com/d/optout > > <https://groups.google.com/d/optout>> . > > > -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. To view this discussion on the web visit https://groups.google.com/d/msgid/machinekit/20190527121558.02c13f85%40edeltraud. For more options, visit https://groups.google.com/d/optout.
