I would agree. I plan to (maybe) use the API one day depending on what it can do and not being limited to the same machine would be beneficial. That being said I may still need to be on the same machine but that's besides the point.
On Mar 2, 2022, 05:58 +0000, Dave McGuire <mcguire@neurotica.com>, wrote:
On 3/1/22 20:16, Paul Koning wrote:
Question for PyDECnet users: as I mentioned, there's a new API, cleaner than the old one. A major addition is access to the Session Control layer, in other words external programs can talk to the API to use DECnet communication services, inbound or outbound. This is how I implemented a simple subset NCP and NFT.

That API runs over a Unix domain socket, in connection mode. It's quite similar to TCP but inherently local to the machine where PyDECnet is running. That's nice for security, of course. But on the other hand, it means that there isn't a way for a PyDECnet running on one machine to offer a portal into DECnet for nearby machines. If you keep a DECnet router in the basement, your laptop can't run NCP since it has no access to that socket.

It would not be all that difficult to add an option for running that same API over a TCP port, possibly with some sort of access filtering. Is there interest in such a thing?

I'm not a PyDECnet user yet, but I will say this, remote
manageability is almost always a good thing.

-Dave

--
Dave McGuire, AK4HZ
New Kensington, PA
_______________________________________________
HECnet mailing list -- hecnet@lists.dfupdate.se
To unsubscribe send an email to hecnet-leave@lists.dfupdate.se