英 [ 'ae?ɡl in ?? 'seɡm?nt ]
美 [ 'ae?ɡ?l ?n ?i 's?ɡm?nt ]
弓形的圆周角
the angle in a circular segment ability
圆周角能力 the angle in a circular segment ability raises teaching design .圆周角能力提高教学设计。
- 基于1个网页
angle in the alternate segment
交错弓形的圆周角 angle between two planes 两平面的交角 angle bisection 角平分 angle bisector 角平分线?;分角线? angle in the alternate segment 交错弓形的圆周角 angle in.
- 基于22个网页
angle in the same segment
同弓形内的圆周角 angle bisection 角平分angle bisector 角平分线 ;分角线 angle in the alternate segment 交错弓形的圆周角angle in the same segment 同弓形内的圆周角.
- 基于23个网页收藏，332 浏览
问题对人有帮助，内容完整，我也想知道答案
问题没有实际价值，缺少关键内容，没有改进余地
上周在segmentfault上面提问了一个问题，提问完之后心想要不在搜索引擎上搜一下问题吧，说不上晚上有答案呢，于是乎我打开百度输入手机输入法闪退，虽然没有找到答案，但是一个意想不到的事情发生了，刚刚编辑的内容竟然立马被百度收录了！详情见下图，可以看到收录发生在3分钟前：.
我查看了这个问题的网页的源代码，有两处代码让我感觉到很可疑，就是：
&link rel="alternate" type="application/atom+xml" title="SegmentFault 最新问题" href="/feeds/questions"&
&link rel="alternate" type="application/atom+xml" title="SegmentFault 最新文章" href="/feeds/blogs"&
我打开一看这两个xml吧最新的问题和文章都给罗列出来了，然后这种xml很有可能是给搜索引擎用的，求大神们指点。
PS:为何我提的问题在网站问题列表中看不到呢？
答案对人有帮助，有参考价值
答案没帮助，是错误的答案，答非所问
2月7日 回答
最终发现搜索引擎确实可以借助web feed来发现新页面，具体参见
答案对人有帮助，有参考价值
答案没帮助，是错误的答案，答非所问
2月2日 回答
SEO最终目的就是让搜索引擎抓取你数据更简单
1.良好的网页结构
2.定期大量更新内容
3.每个网页包含关键词
4.访问速度良好
不过最主要的还是你的网站包含有比较优质的内容。
/feeds/questions和/feeds/blogs是rss订阅，是方便自动rss阅读器的，并非让搜索引擎用。
同步到新浪微博
分享到微博？
与我们一起探索更多的未知
专业的开发者技术社区，为用户提供多样化的线上知识交流，丰富的线下活动及给力的工作机会
加入只需一步
关闭理由：
删除理由：
忽略理由：
推广（招聘、广告、SEO 等）方面的内容
与已有问题重复（请编辑该提问指向已有相同问题）
答非所问，不符合答题要求
宜作评论而非答案
带有人身攻击、辱骂、仇恨等违反条款的内容
无法获得确切结果的问题
非开发直接相关的问题
非技术提问的讨论型问题
其他原因（请补充说明）
举报理由：
推广（招聘、广告、SEO 等）方面的内容
带有人身攻击、辱骂、仇恨等违反条款的内容
与已有问题重复（请编辑该提问指向已有相同问题）
不友善内容
答非所问，不符合答题要求
其他原因（请补充说明）
补充说明：
扫扫下载 App
SegmentFault
一起探索更多未知alternate segment,寻求alternate segment的准确意思._百度作业帮
alternate segment,寻求alternate segment的准确意思.
alternate segment,寻求alternate segment的准确意思.
交错弓形（不确定）
[al·ter·nate || ɔːl'tɜːnət]v.
轮流, 交替; 使轮流, 使交替adj.
轮流的, 交替的; 供选择的; 间隔的; 供替换的''segment
[seg·ment || 'segmənt]n.
部分; 切片, 断片; 部门; 线段v.
分割, 切割; 分割成部分; 切成片alternative_segmentation
alternate segment
内错弓形 alternate angle （交）错角alternate segment 内错弓形alternating series 交错级数
- 基于110个网页
交错弓形 （交）错角alternate segment 交错弓形altitude 高；高度；顶垂线；高线
- 基于21个网页
angle in the alternate segment
交错弓形的圆周角 angle between two planes 两平面的交角 angle bisection 角平分 angle bisector 角平分线?;分角线? angle in the alternate segment 交错弓形的圆周角 angle in.
- 基于22个网页& & Network Working Group J. Zweig Request for Comments: 1145 UIUC C. Partridge BBN February 1990 TCP Alternate Checksum Options Status of This Memo This memo suggests a pair of TCP options to allow use of alternate data checksum algorithms in& & & & & & Network Working Group J. Zweig& & Request for Comments: 1145 UIUC& & C. Partridge& & BBN& & February 1990& & TCP Alternate Checksum Options& & Status of This Memo& & This memo suggests a pair of TCP options to allow use of alternate& & data checksum algorithms in the TCP header. The use of these options& & is experimental, and not recommended for production use.& & Distribution of this memo is unlimited.& & Introduction& & Some members of the networking community have expressed interest in& & using checksum-algorithms with different error detection and& & correction properties than the standard TCP checksum. The option& & described in this memo provides a mechanism to negotiate the use of& & an alternate checksum at connection-establishment time, as well as a& & mechanism to carry additional checksum information for algorithms& & that utilize checksums that are longer than 16 bits.& & Definition of the Options& & The TCP Alternate Checksum Request Option may be sent in a SYN& & segment by a TCP to indicate that the TCP is prepared to both& & generate and receive checksums based on an alternate algorithm.& & During communication, the alternate checksum replaces the regular TCP& & checksum in the checksum field of the TCP header. Should the& & alternate checksum require more than 2 octets to transmit, the& & checksum may either be moved into a TCP Alternate Checksum Data& & Option and the checksum field of the TCP header be sent as 0, or the& & data may be split between the header field and the option. Alternate& & checksums are computed over the same data as the regular TCP checksum& & (see TCP Alternate Checksum Data Option discussion below).& & TCP Alternate Checksum Request Option& & The format of the TCP Alternate Checksum Request Option is:& & +----------+----------+----------+& & | Kind=14 | Length=3 | chksum |& & +----------+----------+----------+& & Here chksum is a number identifying the type of checksum to be used.& & This option is not copied into each fragment, and appears only in the& & first fragment.& & The currently defined values of chksum are:& & 0 -- TCP checksum& & 1 -- 8-bit Fletcher's algorithm (see Appendix I)& & 2 -- 16-bit Fletcher's algorithm (see Appendix II)& & Note that the 8-bit Fletcher algorithm gives a 16-bit checksum and& & the 16-bit algorithm gives a 32-bit checksum.& & Alternate checksum negotiation proceeds as follows:& & A SYN segment used to originate a connection may contain the& & Alternate Checksum Request Option, which specifies an alternate& & checksum-calculation algorithm to be used for the connection. The& & acknowledging SYN-ACK segment may also carry the option.& & If both SYN segments carry the Alternate Checksum Request option,& & and both specify the same algorithm, that algorithm must be used& & for the remainder of the connection. Otherwise, the standard TCP& & checksum algorithm must be used for the entire connection. Thus,& & for example, if one TCP specifies type 1 checksums, and the other& & specifies type 2 checksums, then they will use type 0 (the regular& & TCP checksum). Note that in practice, one TCP will typically be& & responding to the other's SYN, and thus either aclearcase/" target="_blank" >ccepting or& & rejecting the proposed alternate checksum algorithm.& & Any segment with the SYN bit set must always use the standard TCP& & checksum algorithm. Thus the SYN segment will always be& & understood by the receiving TCP. The alternate checksum must not& & be used until the first non-SYN segment. In addition, because RST& & segments may also be received or sent without complete state& & information, any segment with the RST bit set must use the& & standard TCP checksum.& & The option may not be sent in any segment that does not have the& & SYN bit set.& & An implementation of TCP which does not support the option should& & silently ignore it (asRFC1122requires). Ignoring the option& & will force any TCP attempting to use an alternate checksum to use& & the standard TCP checksum algorithm, thus ensuring& & interoperability.& & TCP Alternate Checksum Data Option& & The format of the TCP Alternate Checksum Data Option is:& & +---------+---------+---------+ +---------+& & | Kind=15 |Length=N | data | ... | data |& & +---------+---------+---------+ +---------+& & This field is used only when the alternate checksum that is& & negotiated is longer than 16 bits. These checksums will not fit in& & the checksum field of the TCP header and thus at least part of them& & must be put in an option. Whether the checksum is split between the& & checksum field in the TCP header and the option or the entire& & checksum is placed in the option is determined on a checksum by& & checksum basis.& & The length of this option will depend on the choice of alternate& & checksum algorithm for this connection.& & This option is not copied into each fragment, and appears only in the& & first fragment.& & While computing the alternate checksum, the TCP checksum field and& & the data portion TCP Alternate Checksum Data Option are replaced with& & zeros.& & An otherwise acceptable segment carrying this option on a connection& & using a 16-bit checksum algorithm, or carrying this option with an& & inappropriate number of data octets for the chosen alternate checksum& & algorithm is in error a a RST-segment must be& & generated, and the connection aborted.& & Note the requirement above that RST and SYN segments must always use& & the standard TCP checksum.& & APPENDIX I: The 8-bit Fletcher Checksum Algorithm& & The 8-bit Fletcher Checksum Algorithm is calculated over a sequence& & of data octets (call them D[1] through D[N]) by maintaining 2& & unsigned 1's-complement 8-bit accumulators A and B whose contents are& & initially zero, and performing the following loop where i ranges from& & 1 to N:& & A := A + D[i]& & B := B + A& & It can be shown that at the end of the loop A will contain the 8-bit& & 1's complement sum of all octets in the datagram, and that B will& & contain (N)D[1] + (N-1)D[2] + ... + D[N].& & The octets covered by this algorithm should be the same as those over& & which the standard TCP checksum calculation is performed, with the& & pseudoheader being D[1] through D[12] and the TCP header beginning at& & D[13]. Note that, for purposes of the checksum computation, the& & checksum field itself must be equal to zero.& & At the end of the loop, the A goes in the first byte of the TCP& & checksum and B goes in the second byte.& & Note that, unlike the OSI version of the Fletcher checksum, this& & checksum does not adjust the check bytes so that the receiver& & checksum is 0.& & There are a number of much faster algorithms for calculating the two& & octets of the 8-bit Fletcher checksum. For more information see& & [Sklower89], [Nakassis88] and [Fletcher82]. Naturally, any& & computation which computes the same number as would be calculated by& & the loop above may be used to calculate the checksum. One advantage& & of the Fletcher algorithms over the standard TCP checksum algorithm& & is the ability to detect the transposition of octets/words of any& & size within a datagram.& & APPENDIX II: The 16-bit Fletcher Checksum Algorithm& & The 16-bit Fletcher Checksum algorithm proceeds in precisely the same& & manner as the 8-bit checksum algorithm,, except that A, B and the& & D[i] are 16-bit quantities. It is necessary (as it is with the& & standard TCP checksum algorithm) to pad a datagram containing an odd& & number of octets with a zero octet.& & Result A should be placed in the TCP header checksum field and Result& & B should appear in an TCP Alternate Checksum Data option. This& & option must be present in every TCP header. The two bytes reserved& & for B should be set to zero during the calculation of the checksum.& & The checksum field of the TCP header shall contain the contents of A& & at the end of the loop. The TCP Alternate Checksum Data option must& & be present and contain the contents of B at the end of the loop.& & BIBLIOGRAPHY:& & [BrBoPa89] Braden, R., Borman, D., and C. Partridge, "Computing& & the Internet Checksum", ACM Computer Communication& & Review, Vol. 19, No. 2, pp. 86-101, April 1989.& & [Note that this includes Plummer, W. "IEN-45: TCP& & Checksum Function Design" (1978) as an appendix.]& & [Fletcher82] Fletcher, J., "An Arithmetic Checksum for Serial& & Transmissions", IEEE Transactions on Communication,& & Vol. COM-30, No. 1, pp. 247-252, January 1982.& & [Nakassis88] Nakassis, T., "Fletcher's Error Detection Algorithm:& & How to implement it efficiently and how to avoid the& & most common pitfalls", ACM Computer Communication& & Review, Vol. 18, No. 5, pp. 86-94, October 1988.& & [Sklower89] Sklower, K., "Improving the Efficiency of the OSI& & Checksum Calculation", ACM Computer Communication& & Review, Vol. 19, No. 5, pp. 32-43, October 1989.& & Security Considerations& & Security issues are not addressed in this memo.& & Authors' Addresses& & Johnny Zweig& & Digital Computer Lab& & University of Illinois (UIUC)& & 1304 West Springfield Avenue& & CAMPUS MC 258& & Urbana, IL 61801& & Phone: (217) 333-7937& & EMail:zweig@CS.UIUC.EDU& & Craig Partridge& & Bolt Beranek and Newman Inc.& & 50 Moulton Street& & Cambridge, MA 02138& & Phone: (617) 873-2459& & 原文转自：http://www.ltesting.net
声明：该文章系网友上传分享，此内容仅代表网友个人经验或观点，不代表本网站立场和观点；若未进行原创声明，则表明该文章系转载自互联网；若该文章内容涉嫌侵权，请及时向
上一篇：下一篇：
相关经验教程
的原创经验被浏览，获得 ￥0.005 收益
的原创经验被浏览，获得 ￥0.001 收益
的原创经验被浏览，获得 ￥0.005 收益
的原创经验被浏览，获得 ￥0.001 收益
的原创经验被浏览，获得 ￥0.005 收益
的原创经验被浏览，获得 ￥0.005 收益
的原创经验被浏览，获得 ￥0.005 收益
的原创经验被浏览，获得 ￥0.001 收益
的原创经验被浏览，获得 ￥0.001 收益
的原创经验被浏览，获得 ￥0.005 收益
的原创经验被浏览，获得 ￥0.001 收益
的原创经验被浏览，获得 ￥0.001 收益
的原创经验被浏览，获得 ￥0.005 收益
的原创经验被浏览，获得 ￥0.001 收益
的原创经验被浏览，获得 ￥0.001 收益
的原创经验被浏览，获得 ￥0.001 收益
的原创经验被浏览，获得 ￥0.005 收益
的原创经验被浏览，获得 ￥0.001 收益
的原创经验被浏览，获得 ￥0.001 收益
的原创经验被浏览，获得 ￥0.001 收益
的原创经验被浏览，获得 ￥0.005 收益
的原创经验被浏览，获得 ￥0.001 收益
的原创经验被浏览，获得 ￥0.005 收益
的原创经验被浏览，获得 ￥0.005 收益}