Best practices for configuring name-value pairs

1337Abyssal1337

New Member
We have a UI to take name-value pairs from user and send the list to a designated processor. The processor will retrieve these values and process them. Heaven is the limit to name the value. Looking for some rule/best practice to establish names. I have one approach where the list looks this\[code\]param.no=5param.1=abcdparam.2=efghparam.3=ijklparam.4=mnopparam.5=qrst\[/code\]based on value mentioned in "param.no" the processor can easily find the name-value pairs of parameters and process them.The XML look like this:\[code\]<arguments> <parameter name="param.no" value="http://stackoverflow.com/questions/10426959/5"> <parameter name="param.1" value="http://stackoverflow.com/questions/10426959/value1"> <parameter name="param.2" value="http://stackoverflow.com/questions/10426959/value2"> <parameter name="param.3" value="http://stackoverflow.com/questions/10426959/value3"> <parameter name="param.4" value="http://stackoverflow.com/questions/10426959/value4"> <parameter name="param.5" value="http://stackoverflow.com/questions/10426959/value5"> <parameter name="other" value="http://stackoverflow.com/questions/10426959/other"> <parameter name="abcd" value="http://stackoverflow.com/questions/10426959/xwerwe"><arguments>\[/code\]Any gurus can validate and post back if there is any better approach?
 
Back
Top