The UK Home Automation Archive

Archive Home
Group Home
Search Archive

Advanced Search

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

Class Inheritance

  • Subject: Class Inheritance
  • From: Stuart Booth
  • Date: Sat, 24 May 2003 23:00:00 +0000

On Wed, 21 May 2003 13:53:38 +0100, "Kevin Hawkins"

>Topic 1: A base level 'Status' schema that provides for minimalist
>essential state reporting for the typical devices that are prevalent
>in the HA world. ON OFF LEVEL etc
>Topic 2: Discussion around inheritance of classes - for example if
>the above Class was defined as XAPSTATUS then should xAPStatus.C-Bus
>from xAPSTATUS and further should xAPStatus.C-Bus.Lighting enforce the
>inheritance from the C-Bus class.

Gosh, you know, that strikes me as being really near now you mention
it. I started wondering how you'd specify the 'base' class, but it's
already there, in the type name, isn't it.


I could chuck away a separate class I suggested in the xAP-Audio
schema, that of SliMP3.Transport (although back then I was under the
impression that Classes had to be Class.Type formatted - you
subsequently drew my attention to the fact that a.b.c.d etc is valid).

If I send a message with a Class=xAP-Audio.Transport can I include a
xAP-Audio.Transport.SliMP3 message block in the body of the message? I
am inclined to say no.

If I specify a Class=xAP-Audio.Transport.SliMP3 I should expect any
block from any of the parent classes.

Stuart Booth - a reusable xAP framework for .net

<a href="";></a>

xAP_Development Main Index | xAP_Development Thread Index | xAP_Development 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.