活动目录支持的一些命明标准

由于手头没有什么环境, 只有本2000的AD配置手册, 我就从古董文档里面包含的资料开始找吧...

寻址中URL的标准好像有点老的标准了, 不过不妨碍我们对标准的了解:

除了URL外, 还有传统的UNC格式, 这个格式我找不到资料, 只能把wikipedia上的东西拿来凑数了@_@

Uniform Naming Convention

The UNC, short for Universal Naming Convention or Uniform Naming Convention, specifies a common syntax to describe the location of a network resource, such as a shared file, directory, or printer. The UNC syntax for Windows systems is as follows:

\\ComputerName\SharedFolder\Resource

Note: The UNC syntax is sometimes written with forward slashes. In Windows the forward slashes and back slashes are equivalent, but many programs will accept only backward slashes, and some that will only accept *double* backslashes (ie \\\\ComputerName\\SharedFolder)), especially in quoted string constants, due to the standard use of as a .

The "SharedFolder" is not necessarily the same as what a program on the server would see if it tries to open "\SharedFolder". Instead it is a name assigned to an arbitrary folder by the server when it made it "shared".

Unix-like systems occasionally use a similar syntax, but a requirement that double slashes must be treated as single slashes breaks this.^[] More often this syntax is used:

ComputerName:/SharedFolder/Resource 

or, like with the service name:

smb://ComputerName/SharedFolder/Resource

Some Windows APIs also accepts the "Long UNC":

\\?\UNC\ComputerName\SharedFolder\Resource

The different types of paths in Windows are local file system (LFS), such as C:\File, uniform naming convention (UNC), such as \\Server\Volume\File, and Long UNC or UNCW, such as \\?\C:\File or \\?\UNC\Server\Volume\File. In earlier versions of Windows only the API's that accept "Long UNC" would accept more than 260 characters. This has been fixed in recent versions.

最后一个应该是LDAP的URL格式, 我找到了RFC 2255, 不过这个文档还引用了大量其他文档, 比较重要的是RFC 2253. 要了解LDAP可以baidu, google, 最好还是去看RFC的说明, 下面是2255的网址, 其他的修改下路径名就能访问了: