river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Firmstone <j...@zeus.net.au>
Subject Jini Service Type - Request Add defined TXT record keys
Date Thu, 28 Jan 2010 01:35:36 GMT
Hi,

How would one go about having the following TXT keys added to the jini
service type?

id=<Jini Service ID 128 bit hashcode>
gr=<Comma separated set of groups in which the service wishes to 
participate>

The table below gives the strings that have special meaning in the set:

*String*		*Meaning*
""			public group
"*"			all groups
"*.mobile"		all group names ending in ".mobile"


 From the Jini Discovery and Join Specification:


    *Groups*

    A group is an arbitrary string that acts as a name. Each lookup
    service has a set of zero or more groups associated with it.
    Entities using the multicast request protocol specify a set of
    groups they want to communicate with, and lookup services advertise
    the groups they are associated with using the multicast announcement
    protocol. This allows for flexibility in configuring entities:
    instead of maintaining a set of URLs for specific lookup services
    that needs to be updated if any of the services change address, an
    entity can use a set of group names.

    Although group names are arbitrary strings, it is recommended that
    DNS-style names (for example, "eng.sun.com") be used to avoid name
    conflicts. One group name, represented by the empty string, is
    predefined as the /public/ group. Unless otherwise configured,
    lookup services should default to being members of the public group,
    and discovering entities should attempt to find lookup services in
    the public group.

The recommendation in the Spec for utilising DNS-style names is advised
against, since the group already belongs to a DNS domain, this
information would be a duplication, potentially increasing the work
required to move the location of the group.

In order to utilise DNS-SD for a jini LookupService, this information is
important to identify the jini Service ID and djinn groups to which a
service belongs within a domain.

The Jini Specification and codebase are maintained by the Apache River
project at http://incubator.apache.org/river/RIVER/index.html

Best Regards,

Peter Firmstone.


Mime
View raw message