René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Deprecate/remove the action-flag","articleBody":"As far as I know, the only functionality of the `action` flag is that it lets the backend process command headers recursively. This is also visible in the lines below: on line 311 of the removed code, the method is recursively invoked. This adds unnecessary complexity for no good reason, in my opinion. Without the action flag, it is still possible to send multiple commands at once. For instance, consider the following CQC program (in pseudo-CQC):\r\n\r\n```\r\nCQC Header. Type = CQCType.COMMAND. Length = 3 command headers\r\nCommand Header. Instruction = X. Action = False\r\nCommand Header. Instruction = Y. Action = False\r\nCommand Header. Instruction = Z. Action = False\r\n```\r\n\r\nEven though `action` is set to `False`, all three commands will be executed sequentially. This is my understanding of sequences and the `action` flag. Am I missing something?\r\n\r\nRegarding the trouble with the logic: During the design phase of my project, I consulted Leon to discuss some ideas and possible solutions. At that point, I had some questions regarding sequences. All these questions were answered and there are no problems anymore. In my final implementation, the sequence functionality works perfectly (albeit without the action flag, and without sequence headers).\r\n\r\n_Originally posted by @VictorPrins in https://github.com/SoftwareQuTech/CQC-Python/pull/35_","author":{"url":"https://github.com/AckslD","@type":"Person","name":"AckslD"},"datePublished":"2019-10-23T09:03:40.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/43/CQC-Python/issues/43"}