葡京赌场网址bitbucket的简单利用

  本人于圈《图解HTTP》的时刻,刚开头还对URI和URL的分不是极在意,越到末端更发现区别两者的必要性。

1.假如您都把种修建好的讲话,那么提交上去这样:
没有构建地面仓库的话,那先由包本地,到公的种类路线上后
git init
git remote add origin https://linjiayu@bitbucket.org/昵称/仓库名.git
//这里要专注的是网址可能是ssh的,也恐怕是http的。
记要将种多提交一下重新push为好
git add *
git commit -m ‘commit information’

  英文文档:“A URI is a uniform resource identifier while a URL is a
uniform resource locator. Hence every URL is a URI, abstractly
speaking, but not every URI is a URL. This is because there is another
subcategory of URIs, uniform resource names (URNs), which name
resources but do not specify how to locate them. The mailto, news,
and isbn URIs shown above are examples of URNs.

一旦当github的remote上就来矣文本,会并发谬误。此时该先pull一下,即:
git pull origin master

The conceptual distinction between URIs and URLs is reflected in the
differences between this class and
the URL class.

git push -u origin master

An instance of this class represents a URI reference in the syntactic
sense defined by RFC 2396. A URI may be either absolute or relative. A
URI string is parsed according to the generic syntax without regard to
the scheme, if any, that it specifies. No lookup of the host, if any, is
performed, and no scheme-dependent stream handler is constructed.
Equality, hashing, and comparison are defined strictly in terms of the
character content of the instance. In other words, a URI instance is
little more than a structured string that supports the syntactic,
scheme-independent operations of comparison, normalization, resolution,
and relativization.

2.只要还无地方品种以来:
git clone git@bitbucket.org:昵称/仓库名.git
cd bysjpsecho “# My project’s README” >> README.mdgit
add README.md
git commit -m “Initial commit”
git push -u origin master
横上面就规范。

An instance of
the URL class,
by contrast, represents the syntactic components of a URL together with
some of the information required to access the resource that it
describes. A URL must be absolute, that is, it must always specify a
scheme. A URL string is parsed according to its scheme. A stream handler
is always established for a URL, and in fact it is impossible to create
a URL instance for a scheme for which no handler is available. Equality
and hashing depend upon both the scheme and the Internet address of the
host, if any; comparison is not defined. In other words, a URL is a
structured string that supports the syntactic operation of resolution as
well as the network I/O operations of looking up the host and opening a
connection to the specified resource.”

  中文文档:”URI 是统一资源标识符,而 URL
是合资源定位符。因此,笼统地游说,每个 URL 都是 URI,但不肯定每个 URI
都是 URL。这是坐 URI
还包一个子类,即联合资源名称 (URN),它取名资源而不指定如何稳定资源。上面的 mailtonews 和 isbn URI
都是 URN 的示例。

URI 和 URL
概念上的差体现在此类和 URL 类的两样遭遇。

此类的实例代表由 RFC 2396 定义之语法意义上之一个 URI 引用。URI
可以是绝对的,也可是相对的。对 URI
字符串按照一般语法进行辨析,不考虑她所指定的方案(如果产生)不对主机(如果起)执行搜,也非组织依赖让方案的流动处理程序。相等性、哈希计算和比较还严格地冲实例的字符内容开展定义。换句话说,一个
URI
实例和一个支撑语法意义上之、依赖让方案的比、规范化、解析及相对化计算的组织化字符串差不多。

作为对比,URL 类的实例代表了
URL 的语法有和走访它讲述的资源所用的信。URL
必须是绝对的,即其必须始终指定一个方案。URL
字符串按照该方案进行分析。通常会呢 URL
建立一个注处理程序,实际上无法为免供处理程序的方案创造一个 URL
实例。相等性和哈希计算依赖让方案及主机的 Internet
地址(如果来);没有定义比较。换句话说,URL
是一个构造化字符串,它支持解析的语法运算和查找主机和开辟到指定资源的接连之类的网络
I/O 操作。

  以上是自官方文档对于URI的说明着冒出的,对于URI、URL、URN的区分。简单地圈,可以就此一个表来证明这三者的区分。

名词

特性

URI统一资源标识符

既可以相对地也可以绝对地标识一个资源的地址

URL统一资源定位符

是比URI更具体形式,只能是绝对地标识一个资源的地址

URN统一资源名称

只命名一个资源但不指定如何定位资源

  

  参考网址:https://docs.oracle.com/javase/8/docs/api/java/net/URI.html

       http://download.oracle.com/technetwork/java/javase/6/docs/zh/api/java/net/URI.html