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: xAP directory service


  • Subject: RE: xAP directory service
  • From: "Patrick Lidstone \(Personal E-mail\)" <patrick@xxxxxxxxxxxx>
  • Date: Wed, 27 Apr 2005 23:00:23 +0100




> -----Original Message-----
> From: Stuart Booth [mailto:lists@xxxxxxx]
> Sent: 27 April 2005 19:56
> To: xAP_developer@xxxxxxx
> Subject: Re: [xAP_developer] xAP directory service
>
>
> On Tue, 26 Apr 2005 11:56:59 -0000, "Patrick Lidstone"
> <patrick@xxxxxxx> wrote:
>
> >How about we put together a simple xAP directory service - which
is
> >able to handle simple lookup requests, perhaps against an
> LDAP server,
> >or even just a file - as a means of centralising core
> configuration data?
>
> As in, "Hey, I'm here, who was I before when I was last
> started?" I guess this core config data would be the xAP
> specific stuff like h/r intervals, UIDs etc?
>
> Would I be able to find out which devices can do OSD
> requests, and which schema(s) they respond to? James has a
> mechanism I believe that somebody can say "Hey, who does
> OSD?" and each individual responds.
> Would a directory service do the answering after a xAP node
> was registered?
>
> Would a xAP node register when it starts, or once only until
> explicitly forgotten?
>
> Not had the need for this myself just yet, hence the queries
> to find out what others are after.
>

I think it would work in a way that is analogous to the windows registry.
Anyone could query it, and an app would register at install time, and
optionally update items from time to time. But I think we should start
simple...

Patrick





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.