how to ensure same xml config versions maintained in server and client

Question

0.00/5 (No votes)

See more:

I am looking about how to maintain same version of xml config in both client and server. Meaning I want to make sure at any point of time, xml config maintained in server for that client is same in client application. i.e Client and server should have same version, so that if server publish new changes client should accept as such and use it. Mean while client also can change the values but not tags. Especially doing this in .Net.

Do we need to use xml schema to do this or any other simple way there?

thanks in advance.

Posted 6-Aug-13 19:12pm

DavJes

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2013-08-06T19:59:00

Basically, you should evolve your XML schema only in incremental manner. Besides, you should include version information in the XML itself.

Consider the case when some assembly is newer than the schema of the XML file. If the changes are incremental, the data will lack several item. The code will still process it and new data items will keep their default values. If the assembly reads the XML file, and its schema is newer then the assembly, the code should issue the error message telling the user that the code is obsolete and should be updated.

If you have some obsolete data items (which are not significant in newer version of the code), you should not remove them from schema. You can devise some deprecation mechanism instead. If the obsolete data items presents in older XML, it will be simply ignored with the code, but if the code creates new XML file from the data stored in memory of the newer application, should be skipped in XML, even though they exist in the scheme. You could, for example, use some special "obsolete" or "deprecated" attribute at your data member in you data contract.

These are just general ideas summarizing pretty long experience of maintaining versions of code and data. You can review them and devise your own versioning model.

—SA

DavJes · Answer 2 · 2013-08-07T08:50:00

Solution 2

Hi,

Thanks for the answer. But I am looking for what is the best to have same version of xml config maintained in client and server, where server has rights to update the config, as well client can update via UI the config value. But both has to make sure its updated and maintained the same.

Do we need to use schema validation or just simple xml with version in it as you suggest should be fine ?

thanks

Posted 7-Aug-13 8:50am

DavJes

Comments

Richard C Bishop 7-Aug-13 14:52pm

Be mindful of where you are posting items. In this instance you have posted a comment/question as a solution to your original question. Paradoxical?

DavJes 9-Aug-13 3:27am

sorry about that

Richard C Bishop 9-Aug-13 10:30am

No worries, just a friendly comment so that you may avoid down-voting and abuse reports.