This topic contains 2 replies, has 1 voice, and was last updated by 
Josh Stern November 20, 2022 at 6:48 am.
-
Posts
-
Josh Stern
ModeratorHow do I run a task as user j on system k? Remote what? Credentials stored where??
The traditional OS world mostly recommends structure of TCP/IP sockets connecting sessions on different hosts. If the remote session or socket goes down, they need to be reconfigured. The designs I proposed for Virtual DNS multi-format networking favor an approach which focuses on sequences of messages between different virtual dns agents as primitives. The “localhost” at virtualID_834fnjn23346 can be part of that. My preferred design involves having virtual message delivery & continuous running/scheduling on both local & remote host. But the proposal above assumes cookbooks will be developed for applications which can decide which forms are the best fit to their needs. Software developers learn to think about factories for providing different solutions to each lifecycle stage.
-
Josh Stern
ModeratorThe system should have some kind of flag to specify whether “Run this digital task request” is to be repeated when multiple requests come in or whether it should be run only once, discarding later requests, possible with a log type warning. That said, there must be some facility to keeping track of completed singleton tasks. Forever? That’s silly, so there should be a start time horizon for matching.
The system should be able to handle transfer, merge of tasks from other running instances, up to special compatibility issues – e.g. external dependencies that are “local” or unreachable from the new scheduler host.
You must be logged in to reply to this topic.