Mixed order of DRU's and other config elements (Multiple configs sent to a single Raid Service)

After a little confusion and file scraping, I have come to the conclusion that the Client applications (Whether they are CMD or GUI) actually tell the Raid Service what to do each time.. i.e. the Config file is "Always" sent..

So..
Does the order in which the DRU's (And other elements) have to be in the same order each time - so that the processes give the same results ?

e.g.
1) CMD client create DRU's of A, B, C
2) Web GUI calls rsynch with B,A,C
3) Win Client calls validate with C,A,B

What will the restore attempt to do in after step 2 ?
Will validate succeed in step 3 ?

Will Live store these configs locally to it, and also will it have the flexibility to have more than 1 configuration per service ?
(i.e. internal HDD's config and an external HDD Raid 0 / backup config style thing)

The order does not matter because the UoRs are indexed (Ex: data=DRU1{D:\}|DRU2{E:\}|DRU3{F:\} )

You don't need to send the full config, but you might do that for simplicity.
The parameters required for each task (along with those optional and ignored) are documented here: http://www.openegg.org/referenceFlexRAID.curi

For the WebUI, I created a configuration that keeps track of all this and only sends to the host what's required along with those optional parameters that have been set.