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]

Wildcarding query


  • Subject: Wildcarding query
  • From: "David Buckley" <db@xxxxxxxxxxx>
  • Date: Wed, 22 Dec 2004 10:44:24 -0000



Spec says:

"Unless explicitly specified, the : (colon) sub-address separator is
treated as being synonomous with a . (dot) separator. Exact matching
against a : (colon) is only required in situations where wild card
filtering against just the sub-address element is required."

What does that last bit mean?  When does it apply??

Given a device a.b.c:d.e

a.b.*:*.* would shirley match.  Is this what "explicitly
specified"
means?

But does a.b.c.d.e match it?

How about a.b.*.*.e   or  a.b.c.*.*  or a.b.*.d.*

I'm also a bit hazy on body wilcarding.  In the BSC spec it is clear
that multi-part bodies are permitted (xAPBSC.cmd example), and the xAP
spec says "Any multi-block message [note message not schema] with a
wildcarded header address may optionally include additional target
filter" but the BSC spec makes no mention of body targets.

Is it safe to just generically assume that _any_ body may contain a
target= element?

Finally, the '>' character, it is correct that nothing can follow it
in a wildcard specification?






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.