avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • January 22, 2019, 02:04 AM
  • Proudly celebrating 13 years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: Allocation of .dcupdate namespace to user.  (Read 4254 times)


  • Honorary Member
  • Joined in 2007
  • **
  • default avatar
  • Posts: 29
    • View Profile
    • Donate to Member
Allocation of .dcupdate namespace to user.
« on: February 28, 2008, 03:32 AM »


Have you though of facilitating end user use of the .dcupdate file by reserving a part of the namespace for the user to allocate knowing nothing that you do will trample over it or be ruined by uncoordinated content.

For example, a sub item called "user" in which all user entities are mapped would achieve that end. dcUpdate would just ignore that part of the xml tree, and the user could use it as he wishes.

Perhaps it would be wise to declare a rule on the maximum size of the .dcupdate file, perhaps 10k would exceed reasonable needs.



  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 39,104
    • View Profile
    • Mouser's Software Zone on
    • Read more about this member.
    • Donate to Member
Re: Allocation of .dcupdate namespace to user.
« Reply #1 on: February 28, 2008, 08:56 AM »
the updater should ignore sections it doesnt understand.. i'm very happy to say that dcupdater will never use the <user></user> section, so that is now free to use safely.  same is true for the remote versioninfo.xml files.