The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: Changes to Protocol Docs - a Summary


  • Subject: Re: Changes to Protocol Docs - a Summary
  • From: "Mal Lansell" <mal@xxxxxxxxxxx>
  • Date: Mon, 26 Sep 2005 09:35:14 -0000

If we're going to specify the format of the version number, can I
make an appeal for a 3 part numerals only version e.g 4.12.1543 -
then it would match the version numbering system in the Windows
Installer that most of us use to package our apps.



--- In ukha_xpl@xxxxxxx, Gerry Duprey <gerry@c...> wrote:
> Howdy,
>
> > If the app is in config mode, presumably when it receives
hbeat.request
> > it should respond with a config.app?
>
> The way I've been thinking, I would agree with this (that a
hbeat.request
> got a hbeat.app/basic or config.app/basic back as a response,
depending on
> the devices state).
>
> > Also, to be of any use, the version number would need to be
added to the
> > config.app schema as well as hbeat.app (or we won't have any
version
> > info about programs that are not yet configured).
>
> Related to that, and again, I think this would come as a
recommendation than
> a requirement, does anyone have an opinion on the format of the
version?  I
> can see 1) Leaving it entirely to the developer, 2) suggesting a
V1.0 format
> (version=V1.0) or 3) suggesting a "number" only (i.e.
version=1.0)
>
> My thought right now is that the #3 would be the best way.
>
> Note, by "number" only, I mean the raw version ident.  It
certainly could
> have letters or something, justs no prefixes like "V" or
"Vrsn" or
anything.
>
> Gerry
> --
> Gerry Duprey
> Ann Arbor, MI 48103
> http://www.cdp1802.org





xPL Main Index | xPL Thread Index | xPL Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.