![]() RegisterForZeroConf(fClassFactory,'YourServiceTypeName') (if you are using multiple channels, only one channel can be used for ZeroConf discovery).Īdd following code into the initialization section of your service implementation or uncomment existing line. In your Delphi servers, the following changes are necessary:ĭrop a TROZeroConfRegistration component onto your form, and connect it to your ServerChannel component. (As you will see below, a bit central configuration is needed to allow global discovery outside the LAN). This is all that's needed, and after you rebuild and run your service, it will be discoverable on the local network, provided Bonjour is installed. (if you are using multiple channels, only one channel can be used for ZeroConf discovery)Īdd a attribute to your service implementation. NET servers, the following changes are necessary:ĭrop a ZeroConfRegistration component onto your form, and connect it to your ServerChannel component. Making Your Services DiscoverableĪllowing your services to be discovered requires only two very small changes to your server application. Bonjour for Windows might already be installed on many systems, for example as part of a network printer installation, or iTunes. ![]() Apple's Bonjour implementation is based on open source DNS-SD implementations, and if you do not wish to deploy Bonjour, you can build your own version from the source available at. The preferred option is Bonjour for Windows, which is available and distributable free of charge from Apple at Bonjour for Windows. ![]() This service is available by default on Mac OS X (as Bonjour) and most newer Linux distributions (as Avahi), but needs to be installed manually on Windows machines. Requirementsīecause ZeroConf allows seamless discovery of not just Remoting SDK servers but also other services, it uses a central service running on each machine that coordinates the publication and discovery of services across the network. Whats more, as new servers go online, or existing servers are shut down, clients will automatically learn about the changes and can adapt, for example my connecting to a new server. service type, client applications could then browse for this type and automatically discover both server1 and server2. If these services are advertised through ZeroConf with a custom-defined _M圜oSampleService_rosdk._tcp. Clients could browse for the well-known service type on the network. The basic idea is that a client application would be capable to talk to any service of a given service type, and distinguish between different available choices, using the service name.įor example, you might be deploying three servers offering access to a certain service you are providing, running on servers server1 and server2. In most cases (and by default), this will be the host name of the computer running the server, but it is possible (and depending on the use case might be sensible) to override this from code, so your application can give administrators the option to choose a name. The service name is used to identify the individual instance of a service that is running somewhere on the network. for all services registered through it's ZeroConf support, to make them easier to distinguish, and avoid name conflicts. Remoting SDK extends this to _'name'_rosdk._tcp. In Remoting SDK terminology, this would mean that a service type represents a specific service interface (or possibly group of interfaces) you have defined in your RODL.Īll service type names follow the schema _'name'._tcp., and some predefined (non-RO) types would include _http._tcp. In ZeroConf, service providers (concrete instances of a service) are discovered based on two identifiers: a service type and a service name.Īs the name indicates, the service type is used to uniquely identify the specific type of service, with the idea that services of the same type can be interacted with in the same manner. Registration and discovery of services globally across the internet with minimal configuration and a properly set up DNS server. Simply by running, ROZeroConf enabled services will be discoverable by clients. Basic FunctionalityĪutomated discovery of services on the local network without the need of any central infrastructure or discovery service. ![]() ROZeroConf is based on open standards and also know under the names of DNS-SD (DNS Service Discovery) and Bonjour, and is available on all supported platforms, including Windows, Linux and Xcode. It first shipped in the Summer 2009 releases, for all three editions of Remoting SDK. ROZeroConf is an infrastructure for service discovery that is being added to Remoting SDK. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |