Re^3: handling tasks and customizing flow of tasks using perl

1) are you suggesting reading this : "task=B pretask=makeAServerdown posttask=checkBServer" from some text file.

yes

2) The customizations suggested by you will work if only known action is being called.

yes

If you need arbitrary code execution, write an API for programmers.

I don't see any reason mixing API for programmers and for normal users, nor I don't see use of XML/other formats in API for programmers.

Or, parhaps, I misunderstand the OP.

Comment on Re^3: handling tasks and customizing flow of tasks using perl

Replies are listed 'Best First'.
Re^4: handling tasks and customizing flow of tasks using perl by asham (Novice) on Sep 29, 2013 at 18:56 UTC
Hi vsespb, thanks for the clarification. in my xml, my idea was that normal users will just change the flow if required. expert users will have additional feature to add pretasks/post tasks. Idea is to identify a solution which supports plug and play/customization and at the same time provides flexibility to the flow. perl/xml solution is just an idea, we can ignore it if we have better solutions available. Btw, updated question with a real life example.	[reply]

Replies are listed 'Best First'.

Re^4: handling tasks and customizing flow of tasks using perl
by asham (Novice) on Sep 29, 2013 at 18:56 UTC

in my xml, my idea was that normal users will just change the flow if required. expert users will have additional feature to add pretasks/post tasks.

Idea is to identify a solution which supports plug and play/customization and at the same time provides flexibility to the flow. perl/xml solution is just an idea, we can ignore it if we have better solutions available.

Btw, updated question with a real life example.

[reply]