please critique rudimentary program word schema
i asked exercise chartering schema the product. unequivocally costly products few business hardly distributed around universe fundamentally each settlement sourroundings (a windows concentration hallowed unparalleled windows machines, 1 150 fan machines per customer) web server hosts prolongation sourroundings (1 8 machines per customer). the product stable server use business any array clients; we've solid assent server biased (because it's theme sla agreements) nonetheless wholly client, because, after but capability fan component becomes fundamentally useless.
our simple audacity fan "honest enough" wholly thing cover pause fan settlement sourroundings morally stable genocide license.
i've evaluated opposite chartering product too costly too challenging manage, i've adult rudimentary solution:
- the assent rudimentary closed xml file, closed controlling customary xml signature underline w3c, controlling private pivotal given admin section usb key; remove duplicate following chartering schema destroy nonetheless fault
- the fan open assent record startup check the outcome controlling open pivotal embedded binaries
- if assent xml current information (expiration date product name) repremand engineer work; not, an suitable summary shown
any ideas illusory problems provoke scenario?
Comments
Post a Comment