Raimund Hocke

> /asynch/... I do not understand the difference to /run/ > /scripts, /images Move to SikulixServer startup options. Agreed, should be there also. But they should also be available for...

Thanks :-) > /asynch/ I understand: build some job-queue with it. What about giving some startup timing as parameter? > I was concerned about accidental script folder changes or unintended...

>> aborting a running script I think running scripts with the SikulixServer can be compared to running unittests: 1. tests are run one after the other 2. each test has...

>> proposed commands I principally agree. Looking at the WebDriver protocol (https://w3c.github.io/webdriver/) I would prefer: (using :item instead of {item}) GET /scripts GET /script/:name GET /script/:name/run GET /script/:name/run?parm1=foo;bar;... ... similar...

> > run and asynch I think it is not needed - this would do the same if sent instantly one after the other `/script/scr1/run` is started `/script/scr2/run` is queued...

> > feedback from script runs GET /task/:name ... will give some information about the run-state of the script (queue position, start time, elapsed time since start, end time, return...

> > GET vs. POST IMHO we should let GET requests return HTML (if needed like for GET /task/:name) and use POST with JSON for scripted/programmed clients, that want to...

> > groups vs. folders I really like the idea: - the server is started with a default script folder being the default group (/script/:name is looked for in this...

> > obsolete start, startp images (should be done inside a script using the image path features)

> > security With the group feature the access to scripts is already restricted by the options given at server start. Runnable scripts have to be prepared by the server...