⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 slpreg.html

📁 SLP协议在linux下的实现。此版本为1.2.1版。官方网站为www.openslp.org
💻 HTML
字号:
<!doctype html public "-//w3c//dtd html 4.0 transitional//en"><html><head>   <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">   <meta name="GENERATOR" content="Mozilla/4.72C-CCK-MCD Caldera Systems OpenLinux [en] (X11; U; Linux 2.2.14 i686) [Netscape]">   <title>OpenSLP - Static Registration File</title></head><body text="#000000" bgcolor="#FFFFFF" link="#0000EE" vlink="#551A8B" alink="#FF0000"><h2>The Static Registration File</h2><hr WIDTH="100%"><p>Often it will be very useful for OpenSLP users to be able to staticallyregister legacy services (applications that were not compiled to use theSLP library).&nbsp; To accommodate this need <a href="../../rfc/rfc2614.txt">RFC2614</a> specifies a syntax for a registration file that is read by theOpenSLP daemon (slpd).&nbsp; All of the registrations from the registrationfile are maintained by slpd and will remain registered as long as slpdis alive.&nbsp; The default location for the registration can be changedfrom <tt>/etc/slp.reg</tt>to another location using the <a href="CommandLine.html">-rcommand line option</a><tt>.&nbsp; slpd reads the slp.reg </tt>file onstartup and re-reads it when ever the SIGHUP signal is received.<h3><tt>Syntax</tt></h3>The registration file format is pretty easy to understand.&nbsp; It canget complicated so if you have any questions after reading this pleaseconsult <a href="../../rfc/rfc2614.txt">RFC 2614.</a>Each registration consists of several lines with the following format:<br>&nbsp;<blockquote><b><tt>#comment</tt></b><br><b><tt>;comment</tt></b><br><b><tt>service-url,language-tag,lifetime,[service-type]&lt;newline></tt></b><br><b><tt>"scopes="[scope-list]&lt;newline></tt></b><br><b><tt>[attrid]"="val1&lt;newline></tt></b><br><b><tt>[attrid]"="val1,val2,val3&lt;newline></tt></b><br><b><tt>&lt;newline></tt></b></blockquote><p><br><b><tt>service-url</tt></b><blockquote>(Required) The service-url which must follow the Service URLsyntax explained <a href="#Service URL Syntax">below</a>.</blockquote><b><tt>language-tag</tt></b><blockquote>(Required) The language-tag uses the (two character) languagetags as specified by <a href="../../rfc/rfc1766.txt">RFC1766</a> ("en" "fr", "de", etc...)</blockquote><b><tt>lifetime</tt></b><blockquote>(Required) The lifetime of the registration in seconds.&nbsp;Value must be between 0 and 65535.&nbsp; Use 65535 if you want the registrationto be maintained for the life of slpd.</blockquote><b><tt>service-type</tt></b><blockquote>(Optional) The type of service being registered.&nbsp; Ignoredby OpenSLP because service-url must conform to the SLP Service URL format.</blockquote><b><tt>scope-list</tt></b><blockquote>(Optional) List of comma delimited scopes to register the servicein.&nbsp; If omitted then service is registered in all scopes specifiedby the <tt><a href="SlpConf.html">slp.conf</a></tt>file.</blockquote><b><tt>attrs</tt></b><blockquote>(Optional) The attributes to register along with the service.&nbsp;Any string but "scopes" or "SCOPES" can be used as an attrid.&nbsp; Notethat the '"' character has no real significance.&nbsp; Strings should not bequoted!</blockquote><h3>Examples</h3>Several examples of registration entries are provided below:<br>&nbsp;<blockquote><tt>#Register a OpenSLP testing service</tt><br><tt>service:test.openslp://192.168.100.1,en,65535</tt><br><tt>scopes=test1,test2</tt><br><tt>description=OpenSLP Testing Service</tt><br><tt>authors=mpeterson,jcarey</tt><p><tt>#Register ssh service</tt><br><tt>service:ssh.openslp://192.168.100.1,en,65535</tt><br><tt>#use default scopes</tt><br><tt>description=Secure Shell</tt><p><tt>#Register telnet service with no attributes</tt><br><tt>service:telnet.myorg://192.168.100.1,en,65535</tt><br><tt>#use default scopes</tt></blockquote><h3><a NAME="Service URL Syntax"></a>Service URL Syntax</h3>If you decide to use Service URLs extensively, you should probablyread <a href="../../rfc/rfc2609.txt">RFC 2609</a>,but if you just want to know what they look like, the following explanationshould be good enough:<blockquote><tt>service-url = "service:"&lt;service-type>"://"&lt;addrspec></tt></blockquote>The service-type is a service type as explained <a href="#SLP Service Type Syntax">below</a>.addrspec can be just about anything you want that fits URL syntax (see<a href="../../rfc/rfc2396.txt">RFC 2396</a>) and can be translated as a network location.&nbsp; The "<tt>service:</tt>"and "<tt>://</tt>" strings are required.<p><b>Service URL Examples</b><p><tt>service:weather.nasa:wtp://weather.nasa.com:12000</tt><br><tt>service:weather.nasa:swtp://weather.nasa.com:12001</tt><br><tt>service:chat.superchat://chat.superchat.com;auth=ldap</tt><br>&nbsp;<h3><a NAME="SLP Service Type Syntax"></a>SLP Service Type Syntax</h3>The official definition of Service Type strings can be found in <a href="../../rfc/rfc2609.txt">RFC 2609</a>, "Service Templates and Service Schemes".&nbsp; If you will beworking with "well known" (IANA) service types, you should read it.&nbsp;If you are developing applications for "proprietary" services then youwill probably be satisfied with the following explanation:<p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; <tt>service-type = &lt;abstract-type.naming-authority>":"&lt;concrete-type></tt><p>The abstract-type is simple (hopefully short) descriptive string thatdescribes the type of service.&nbsp; The naming-authority is the name (hopefullyunique) name of the organization that named the service.&nbsp; The naming-authorityis optional, but if it is omitted then IANA is assumed to be the namingauthority and IANA requires service-types to be registered (see <a href="../../rfc/rfc2609.txt">RFC 2609</a>).&nbsp; The concrete-type is also optional.&nbsp; Think of a concrete-typeas a kind of sub-type of the abstract-type.&nbsp; For example, "printer"is an abstract type (owned by IANA) and "printer:lpr" is a concrete type(owned by IANA).<p><b>Service Type Examples</b><p><tt>weather.nasa:wtp</tt>&nbsp; - A (fictitious) weather service typeowned by NASA that uses Weather Transfer protocol<br>weather.nasa:swtp - A (fictitious) weather service type owned by NASAthat uses Simple Weather Transfer protocol.<br><tt>chat.superchat</tt> - A chat service type owned by SuperChat<br><tt>printer.samba</tt> - A samba printer service type<br><tt>ftp</tt> - An IANA ftp service type<br><tt>telnet</tt> - An IANA telnet service type<br>&nbsp;</body></html>

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -