Hello,
I have an upcoming task to do that I think might be perfect for XML, but I'd like someone's educated opinion - I am very new to XML concepts.
We're a company that makes little handheld devices (and other kinds of devices) that all have reflashable/updatable microcode built into them. We have 4 models of handheld devices, but will be adding new devices fairly quickly in the future.
We want selected partner/developers (who write 3rd party applications) to enable their software to 'finger/ftp' our company's website, locate the latest code build for a given model of handheld, grab the code, and update the device (assume one of our devices is physically connected to the PC running the 3rd party app).
One way we could achieve this is to just assign and publish to the developers an arbitrary directory and naming structure, such as:
<!-- m --><a class="postlink" href="http://www.xyzcompany.com/codeupdates/handheld1/codeupdate1.bin">http://www.xyzcompany.com/codeupdates/h ... pdate1.bin</a><!-- m -->
<!-- m --><a class="postlink" href="http://www.xyzcompany.com/codeupdates/handheld1/codeupdate2.bin">http://www.xyzcompany.com/codeupdates/h ... pdate2.bin</a><!-- m -->
<!-- m --><a class="postlink" href="http://www.xyzcompany.com/codeupdates/handheld1/codeupdate3.bin">http://www.xyzcompany.com/codeupdates/h ... pdate3.bin</a><!-- m -->
and proceed thusly:
<!-- m --><a class="postlink" href="http://www.xyzcompany.com/codeupdates/handheld2/codeupdate1.bin">http://www.xyzcompany.com/codeupdates/h ... pdate1.bin</a><!-- m -->
<!-- m --><a class="postlink" href="http://www.xyzcompany.com/codeupdates/handheld2/codeupdate2.bin">http://www.xyzcompany.com/codeupdates/h ... pdate2.bin</a><!-- m -->
etc.
But is this the best approach? Is there an XML wrapper we could adopt that would position our company and the developers better? If so, what would be the advantages?
Assuming our 3rd party developers also have limited experience with XML, would it be best for our company to supply them with code examples or a 'reader framework' of sorts in order to more easily make their apps XML compliant?
Finally, is there a software/code library out there that would make this task easier for my company and the developers?
Thanks much,
Tom
I have an upcoming task to do that I think might be perfect for XML, but I'd like someone's educated opinion - I am very new to XML concepts.
We're a company that makes little handheld devices (and other kinds of devices) that all have reflashable/updatable microcode built into them. We have 4 models of handheld devices, but will be adding new devices fairly quickly in the future.
We want selected partner/developers (who write 3rd party applications) to enable their software to 'finger/ftp' our company's website, locate the latest code build for a given model of handheld, grab the code, and update the device (assume one of our devices is physically connected to the PC running the 3rd party app).
One way we could achieve this is to just assign and publish to the developers an arbitrary directory and naming structure, such as:
<!-- m --><a class="postlink" href="http://www.xyzcompany.com/codeupdates/handheld1/codeupdate1.bin">http://www.xyzcompany.com/codeupdates/h ... pdate1.bin</a><!-- m -->
<!-- m --><a class="postlink" href="http://www.xyzcompany.com/codeupdates/handheld1/codeupdate2.bin">http://www.xyzcompany.com/codeupdates/h ... pdate2.bin</a><!-- m -->
<!-- m --><a class="postlink" href="http://www.xyzcompany.com/codeupdates/handheld1/codeupdate3.bin">http://www.xyzcompany.com/codeupdates/h ... pdate3.bin</a><!-- m -->
and proceed thusly:
<!-- m --><a class="postlink" href="http://www.xyzcompany.com/codeupdates/handheld2/codeupdate1.bin">http://www.xyzcompany.com/codeupdates/h ... pdate1.bin</a><!-- m -->
<!-- m --><a class="postlink" href="http://www.xyzcompany.com/codeupdates/handheld2/codeupdate2.bin">http://www.xyzcompany.com/codeupdates/h ... pdate2.bin</a><!-- m -->
etc.
But is this the best approach? Is there an XML wrapper we could adopt that would position our company and the developers better? If so, what would be the advantages?
Assuming our 3rd party developers also have limited experience with XML, would it be best for our company to supply them with code examples or a 'reader framework' of sorts in order to more easily make their apps XML compliant?
Finally, is there a software/code library out there that would make this task easier for my company and the developers?
Thanks much,
Tom