HTTP1.1 Notes 8, Header Field Definitions

[url]http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14[/url]

[b]Accept[/b]
The Accept request-header field can be used to specify certain media types which are acceptable for the response

Accept = "Accept" ":"
#( media-range [ accept-params ] )

media-range = ( "*/*"
| ( type "/" "*" )
| ( type "/" subtype )
) *( ";" parameter )
accept-params = ";" "q" "=" qvalue *( accept-extension )
accept-extension = ";" token [ "=" ( token | quoted-string ) ]

[b]Accept-Charset[/b]
The Accept-Charset request-header field can be used to indicate what character sets are acceptable for the response

Accept-Charset = "Accept-Charset" ":"
1#( ( charset | "*" )[ ";" "q" "=" qvalue ] )

[b]Accept-Encoding[/b]
The Accept-Encoding request-header field is similar to Accept, but restricts the content-codings that are acceptable in the response

Accept-Encoding = "Accept-Encoding" ":"

1#( codings [ ";" "q" "=" qvalue ] )
codings = ( content-coding | "*" )

[b]Accept-Language[/b]
The Accept-Language request-header field is similar to Accept, but restricts the set of natural languages that are preferred as a response to the request

Accept-Language = "Accept-Language" ":"
1#( language-range [ ";" "q" "=" qvalue ] )
language-range = ( ( 1*8ALPHA *( "-" 1*8ALPHA ) ) | "*" )

[b]Accept-Ranges[/b]
The Accept-Ranges response-header field allows the server to indicate its acceptance of range requests for a resource

Accept-Ranges = "Accept-Ranges" ":" acceptable-ranges
acceptable-ranges = 1#range-unit | "none"

[b]Age[/b]
The Age response-header field conveys the sender's estimate of the amount of time since the response (or its revalidation) was generated at the origin server

Age = "Age" ":" age-value
age-value = delta-seconds

[b]Allow[/b]
The Allow entity-header field lists the set of methods supported by the resource identified by the Request-URI

Allow = "Allow" ":" #Method

[b]Authorization[/b]
A user agent that wishes to authenticate itself with a server--usually, but not necessarily, after receiving a 401 response--does so by including an Authorization request-header field with the request

Authorization = "Authorization" ":" credentials

[b]Cache-Control[/b]
The Cache-Control general-header field is used to specify directives that MUST be obeyed by all caching mechanisms along the request/response chain

Cache-Control = "Cache-Control" ":" 1#cache-directive

cache-directive = cache-request-directive
| cache-response-directive

cache-request-directive =
"no-cache"
| "no-store"
| "max-age" "=" delta-seconds
| "max-stale" [ "=" delta-seconds ]
| "min-fresh" "=" delta-seconds
| "no-transform"
| "only-if-cached"
| cache-extension

cache-response-directive =
"public"
| "private" [ "=" <"> 1#field-name <"> ]
| "no-cache" [ "=" <"> 1#field-name <"> ]
| "no-store"
| "no-transform"
| "must-revalidate"
| "proxy-revalidate"
| "max-age" "=" delta-seconds
| "s-maxage" "=" delta-seconds
| cache-extension

cache-extension = token [ "=" ( token | quoted-string ) ]

[b]Connection[/b]
The Connection general-header field allows the sender to specify options that are desired for that particular connection and MUST NOT be communicated by proxies over further connections

Connection = "Connection" ":" 1#(connection-token)
connection-token = token

[b]Content-Encoding[/b]
The Content-Encoding entity-header field is used as a modifier to the media-type

Content-Encoding = "Content-Encoding" ":" 1#content-coding

[b]Content-Language[/b]
The Content-Language entity-header field describes the natural language(s) of the intended audience for the enclosed entity

Content-Language = "Content-Language" ":" 1#language-tag

[b]Content-Length[/b]
The Content-Length entity-header field indicates the size of the entity-body, in decimal number of OCTETs, sent to the recipient or, in the case of the HEAD method, the size of the entity-body that would have been sent had the request been a GET

Content-Length = "Content-Length" ":" 1*DIGIT

[b]Content-Location[/b]
The Content-Location entity-header field MAY be used to supply the resource location for the entity enclosed in the message when that entity is accessible from a location separate from the requested resource's URI

Content-Location = "Content-Location" ":"
( absoluteURI | relativeURI )

[b]Content-MD5[/b]
The Content-MD5 entity-header field, as defined in RFC 1864 [23], is an MD5 digest of the entity-body for the purpose of providing an end-to-end message integrity check (MIC) of the entity-body

Content-MD5 = "Content-MD5" ":" md5-digest
md5-digest = <base64 of 128 bit MD5 digest as per RFC 1864>

[b]Content-Range[/b]
The Content-Range entity-header is sent with a partial entity-body to specify where in the full entity-body the partial body should be applied

Content-Range = "Content-Range" ":" content-range-spec

content-range-spec = byte-content-range-spec
byte-content-range-spec = bytes-unit SP
byte-range-resp-spec "/"
( instance-length | "*" )

byte-range-resp-spec = (first-byte-pos "-" last-byte-pos)
| "*"
instance-length = 1*DIGIT

[b]Content-Type[/b]
The Content-Type entity-header field indicates the media type of the entity-body sent to the recipient or, in the case of the HEAD method, the media type that would have been sent had the request been a GET

Content-Type = "Content-Type" ":" media-type

[b]Date[/b]
The Date general-header field represents the date and time at which the message was originated, having the same semantics as orig-date in RFC 822

Date = "Date" ":" HTTP-date

[b]ETag[/b]
The ETag response-header field provides the current value of the entity tag for the requested variant

ETag = "ETag" ":" entity-tag

[b]Expect[/b]
The Expect request-header field is used to indicate that particular server behaviors are required by the client

Expect = "Expect" ":" 1#expectation

expectation = "100-continue" | expectation-extension
expectation-extension = token [ "=" ( token | quoted-string )
*expect-params ]
expect-params = ";" token [ "=" ( token | quoted-string ) ]

[b]Expires[/b]
The Expires entity-header field gives the date/time after which the response is considered stale

Expires = "Expires" ":" HTTP-date

[b]From[/b]
The From request-header field, if given, SHOULD contain an Internet e-mail address for the human user who controls the requesting user agent

From = "From" ":" mailbox

[b]Host[/b]
The Host request-header field specifies the Internet host and port number of the resource being requested, as obtained from the original URI given by the user or referring resource

Host = "Host" ":" host [ ":" port ]

[b]If-Match[/b]
The If-Match request-header field is used with a method to make it conditional

If-Match = "If-Match" ":" ( "*" | 1#entity-tag )

[b]If-Modified-Since[/b]
The If-Modified-Since request-header field is used with a method to make it conditional: if the requested variant has not been modified since the time specified in this field, an entity will not be returned from the server; instead, a 304 (not modified) response will be returned without any message-body

If-Modified-Since = "If-Modified-Since" ":" HTTP-date

[b]If-None-Match[/b]
The If-None-Match request-header field is used with a method to make it conditional

If-None-Match = "If-None-Match" ":" ( "*" | 1#entity-tag )

[b]If-Range[/b]
If a client has a partial copy of an entity in its cache, and wishes to have an up-to-date copy of the entire entity in its cache, it could use the Range request-header with a conditional GET

If-Range = "If-Range" ":" ( entity-tag | HTTP-date )

[b]If-Unmodified-Since[/b]
The If-Unmodified-Since request-header field is used with a method to make it conditional

If-Unmodified-Since = "If-Unmodified-Since" ":" HTTP-date

[b]Last-Modified[/b]
The Last-Modified entity-header field indicates the date and time at which the origin server believes the variant was last modified

Last-Modified = "Last-Modified" ":" HTTP-date

[b]Location[/b]
The Location response-header field is used to redirect the recipient to a location other than the Request-URI for completion of the request or identification of a new resource

Location = "Location" ":" absoluteURI

[b]Max-Forwards[/b]
The Max-Forwards request-header field provides a mechanism with the TRACE and OPTIONS methods to limit the number of proxies or gateways that can forward the request to the next inbound server

Max-Forwards = "Max-Forwards" ":" 1*DIGIT

[b]Pragma[/b]
The Pragma general-header field is used to include implementation- specific directives that might apply to any recipient along the request/response chain

Pragma = "Pragma" ":" 1#pragma-directive
pragma-directive = "no-cache" | extension-pragma
extension-pragma = token [ "=" ( token | quoted-string ) ]

[b]Proxy-Authenticate[/b]
The Proxy-Authenticate response-header field MUST be included as part of a 407 (Proxy Authentication Required) response

Proxy-Authenticate = "Proxy-Authenticate" ":" 1#challenge

[b]Proxy-Authorization[/b]
The Proxy-Authorization request-header field allows the client to identify itself (or its user) to a proxy which requires authentication

Proxy-Authorization = "Proxy-Authorization" ":" credentials

[b]Range[/b]
HTTP retrieval requests using conditional or unconditional GET methods MAY request one or more sub-ranges of the entity, instead of the entire entity, using the Range request header, which applies to the entity returned as the result of the reques

Range = "Range" ":" ranges-specifier
ranges-specifier = byte-ranges-specifier
byte-ranges-specifier = bytes-unit "=" byte-range-set
byte-range-set = 1#( byte-range-spec | suffix-byte-range-spec )
byte-range-spec = first-byte-pos "-" [last-byte-pos]
first-byte-pos = 1*DIGIT
last-byte-pos = 1*DIGIT
suffix-byte-range-spec = "-" suffix-length
suffix-length = 1*DIGIT

[b]Referer[/b]
The Referer[sic] request-header field allows the client to specify, for the server's benefit, the address (URI) of the resource from which the Request-URI was obtained

Referer = "Referer" ":" ( absoluteURI | relativeURI )

[b]Retry-After[/b]
The Retry-After response-header field can be used with a 503 (Service Unavailable) response to indicate how long the service is expected to be unavailable to the requesting client

Retry-After = "Retry-After" ":" ( HTTP-date | delta-seconds )

[b]Server[/b]
The Server response-header field contains information about the software used by the origin server to handle the request

Server = "Server" ":" 1*( product | comment )

[b]TE[/b]
The TE request-header field indicates what extension transfer-codings it is willing to accept in the response and whether or not it is willing to accept trailer fields in a chunked transfer-coding

TE = "TE" ":" #( t-codings )
t-codings = "trailers" | ( transfer-extension [ accept-params ] )

[b]Trailer[/b]
The Trailer general field value indicates that the given set of header fields is present in the trailer of a message encoded with chunked transfer-coding

Trailer = "Trailer" ":" 1#field-name

[b]Transfer-Encoding[/b]
The Transfer-Encoding general-header field indicates what (if any) type of transformation has been applied to the message body in order to safely transfer it between the sender and the recipient

Transfer-Encoding = "Transfer-Encoding" ":" 1#transfer-coding

[b]Upgrade[/b]
The Upgrade general-header allows the client to specify what additional communication protocols it supports and would like to use if the server finds it appropriate to switch protocols

Upgrade = "Upgrade" ":" 1#product

[b]User-Agent[/b]
The User-Agent request-header field contains information about the user agent originating the request

User-Agent = "User-Agent" ":" 1*( product | comment )

[b]Vary[/b]
The Vary field value indicates the set of request-header fields that fully determines, while the response is fresh, whether a cache is permitted to use the response to reply to a subsequent request without revalidation

Vary = "Vary" ":" ( "*" | 1#field-name )

[b]Via[/b]
The Via general-header field MUST be used by gateways and proxies to indicate the intermediate protocols and recipients between the user agent and the server on requests, and between the origin server and the client on responses

Via = "Via" ":" 1#( received-protocol received-by [ comment ] )
received-protocol = [ protocol-name "/" ] protocol-version
protocol-name = token
protocol-version = token
received-by = ( host [ ":" port ] ) | pseudonym
pseudonym = token

[b]Warning[/b]
The Warning general-header field is used to carry additional information about the status or transformation of a message which might not be reflected in the message

Warning = "Warning" ":" 1#warning-value

warning-value = warn-code SP warn-agent SP warn-text
[SP warn-date]

warn-code = 3DIGIT
warn-agent = ( host [ ":" port ] ) | pseudonym
; the name or pseudonym of the server adding
; the Warning header, for use in debugging
warn-text = quoted-string
warn-date = <"> HTTP-date <">

[b]WWW-Authenticate[/b]
The WWW-Authenticate response-header field MUST be included in 401 (Unauthorized) response messages

WWW-Authenticate = "WWW-Authenticate" ":" 1#challenge

太多了,足足47个header filed,细节以后遇到再来看吧
MuleSoft+LLM企业级AI编排:合规、可审计、可落地的集成实践 企业级AI编排是指将大语言模型(LLM)深度嵌入现有IT系统,通过成熟集成平台实现连接治理、状态管理与端到端可观测性。其核心原理在于用确定性流程约束非确定性模型输出,依托RAG增强、Prompt版本化、上下文透传与输出Schema校验等机制保障结果可信。技术价值体现在降低幻觉风险、满足ISO 27001等合规审计要求,并显著提升AI介入环节的可验证性与可回滚性。典型应用场景包括智能合同审核、跨系统工单联动、GDPR条款提取等需强事务性与高责任追溯的业务流。本文聚焦MuleSoft与Azure OpenAI协 阅读详情

相关推荐

Obsidian双模型AI工作流:Claudian调度原理与安全配置

Obsidian作为知识管理核心,其AI能力并非简单接入大模型即可实现。真正的工程化落地需理解模型能力边界、上下文调度机制与本地沙箱安全模型。Claude Code专精代码语义解析与AST感知,适合函数补全、重构与错误定位;Codex强于结构化输出与跨模态指令理解,适用于YAML生成、多笔记联动与Front Matter智能更新。Claudian本质是轻量级调度中间件,通过任务识别路由、上下文注入与响应归一化,将二者能力无缝嵌入编辑流。该架构不依赖云端服务,所有文件访问、命令执行均受最小权限白名单控制,符合

weixin_33965305的博客 300

RFC2616-HTTP1.1-Header Field Definitions(头字段规定部分—译文)

part ofHypertext Transfer Protocol -- HTTP/1.1 RFC 2616 Fielding, et al. 14 头字段规定   该章节定义了HTTP1.1标准所包含的所有头字段的相关语法和含义。实体头字段是接收者或者发送者所涉及到的,并不区分是客户端还是服务器所拥有,而是依据是谁发送或者是谁接受该实体的字段。 14.1Accept   Acce...

weixin_30799995的博客 483

ChatGPT API新手实战指南:从密钥配置到流式响应避坑全解析

OpenAI API 是基于 REST 架构的通用人工智能服务接口,其核心原理是通过标准 HTTP 请求(含 Authorization 头、JSON Body 和严格路径)与模型服务通信。技术价值在于将大语言模型能力解耦为可编程、可监控、可集成的云服务,支撑智能客服、内容生成、结构化数据提取等工程场景。但真实落地常卡在非功能层面:API密钥管理不当导致权限泄露或401错误,stream流式响应因未正确解析 SSE 协议而截断或阻塞。本文聚焦 Python 工程实践,覆盖密钥安全绑定、Headers/Bod

weixin_30470643的博客 527

HTTP/1.1: Header Field Definitions

HTTP/1.1: Header Field Definitions HTTP/1.1: Header Field Definitions14.44 VaryThe Vary field value indicates the set of request-head...

136

随机森林调参指南:核心参数解析与工业实践

随机森林作为集成学习的经典算法,通过构建多棵决策树并综合其预测结果来提升模型性能。其核心优势在于通过特征和样本的随机性(max_features参数)实现天然的抗过拟合能力,同时保持较好的解释性。在工程实践中,合理调整n_estimators(树的数量)、max_depth(树深度)等关键参数,可使模型性能提升20%-30%。特别是在金融风控、医疗诊断等高价值场景中,配合GridSearchCV网格搜索或贝叶斯优化等自动化调参技术,能显著提升模型在准确率、召回率等关键指标的表现。本文深入解析了随机森林的调参

hideto 213

【7】ipmi sdr & sel log

sensor type是cpu/内存/psu/fan等哪一类,sdr(sensor的数据结构)被组件监控PLDM延续,类似配置文件即静态存储,bmc根据这配置文件去展示sensor数值:温度功耗都是连续值是阈值sensor(43.1),状态型的sdr(43.2)如风扇有没有故障和在位,43.3:记一个sel日志必然对应一个sdr,但是这个sdr不想显示当前状态,只是用来记一条sel日志用的,就可以是这个类型,比compact(压缩)记录东西更少。 如下分HEADER/KEY/BODY,sensor num

持续更新ing... 1024

RFC2616-HTTP1.1-Header Field Definitions(头字段规定部分—单词注释版)

part ofHypertext Transfer Protocol -- HTTP/1.1RFC 2616 Fielding, et al. 14Header Field Definitions(规定) This section(部分,章节) defines(规定定义)the syntax(语法)and semantics(语意)of a...

weixin_33831196的博客 482

基于 AUTOSAR 的域控产品软件开发进阶探索

本文深入探讨了AUTOSAR架构在汽车域控产品开发中的进阶应用。首先从系统设计角度分析了AUTOSAR分层架构原理及其在域控产品中的优化部署策略;其次详细介绍了Davinci和EBTresos等主流工具链的特点与协同使用方法;然后重点阐述了ASPICE流程与功能安全/信息安全标准的实施要点;最后分享了多核车载芯片(如NXP S32G)的适配经验与优化实践。通过架构设计、工具运用、标准遵循和芯片适配四个维度的专业解析,为域控产品的AUTOSAR开发提供了系统性指导。

SiArch的博客 1199

leveldb资料整理

[b]leveldb介绍[/b] [url]http://code.google.com/p/leveldb/[/url] [url]http://en.wikipedia.org/wiki/LevelDB[/url] [url]http://highscalability.com/blog/2011/8/10/leveldb-fast-and-lightweight-keyvalue-da...

hideto 761

华为防火墙USG6600全流量日志配置指南:从流量监控到NAT日志的完整方案

本文详细介绍了华为USG6600防火墙全流量日志配置方案,涵盖流量监控、NAT日志及安全事件溯源等核心功能。通过精细化配置和性能优化技巧,帮助企业构建高效、合规的日志体系,提升网络安全运维效率。文章特别强调了日志采样与字段过滤的实用方法,适用于高流量环境下的资源优化。

gin88的博客 348

XCP_Basic 移植步骤

XCP_Basic 移植步骤

ggzzc的博客 2316

Web搜索引擎原理和技术

主要的三个功能模块:网页搜集、预处理、查询服务 基本要求:在一个[b]可以接受的时间[/b]内返回一个和该用户查询[b]匹配[/b]的网页信息[b]列表[/b],列表的每一条目至少包含三个元素--标题、网址链接、摘要 [b]网页搜集[/b] 网页搜集的两种方式:定期搜集,增量搜集 一种搜集方式是将Web上的网页集合看成是一个有向图,搜集过程从给定起始URL集合S开始,沿着网页中...

hideto 616

uniapp 使用摄像头 live-pusher (APP)

uniapp 中开发 app 时使用live-pusher踩过的坑

随身笔记 1万+

锂离子电池过压保护与BQ2920芯片应用解析

锂离子电池因其高能量密度广泛应用于电子设备,但过压充电会引发安全隐患。过压保护(OVP)电路通过实时监测电池电压,在超过阈值时切断充电回路,防止热失控。BQ29200作为专用保护芯片,采用双比较器架构实现快速响应,并具备电量平衡功能,有效解决串联电池组的电压不均衡问题。结合PIC18F4585微控制器,可构建多级保护系统,实现从硬件保护到软件预警的完整解决方案。这类技术在便携设备、储能系统等领域尤为重要,特别是在需要高可靠性的电动工具和新能源应用中。通过优化延迟时间和平衡电流等参数,可以进一步提升系统安全性

hideto 487

JeecgBoot passwordChange 任意用户密码重置漏洞复现

​JeecgBoot 框架passwordChange接口存在任意用户密码重置漏洞,未经身份验证的远程攻击者可以利用此漏洞重置管理员账户密码,从而接管系统后台,造成信息泄露,导致系统处于极不安全的状态。

0xSec 2641

黑猫带你学eMMC协议第17篇:超详细的eMMC HS200 & HS400讲解

1 前言 1.1 声明 本文依据eMMC JEDEC5.1及个人工作经验整理而成,如有错误请留言。 本文结合eMMC JEDEC5.1协议手册查看效果更佳。 1.2 内容提要 本文大约6000字,主要内容有: 1.什么是emmc hs200/hs400? 2.什么是tuning?tuning的过程又是什么? 3.如何设置才能让emmc进入hs200 mode? 4.如何设置才能让emmc进入hs400 mode? 5.emmc关于HS200/HS400内部结构框图对比。 6.部分个人相关经验总结。

黑猫奥利奥的博客 1万+

AI如何重塑教育论文数据分析:从数据清洗到可视化

数据分析在教育研究中扮演着关键角色,其质量直接影响论文结论的可信度。传统方法常面临主观偏差、统计方法选择困难等问题。现代AI技术通过算法模型实现了数据处理的自动化与智能化,如智能数据清洗模块能自动识别异常值,动态统计方法推荐系统则帮助非统计学背景的研究者选择合适分析方法。这些技术创新不仅提升了研究效率,还增强了结果的可视化呈现,如教育领域特有的桑基图和成长曲线图。特别是在教育论文写作中,AI工具如'数据炼金术士'通过三层处理架构(专用模型训练、专业算法整合、领域分析模板)显著提升了数据分析的准确性和学术价值

hideto 461

OpenClaw 在 Docker 容器中的部署实战——零配置启动

本文介绍了OpenClaw在Docker容器中的快速部署方法,对比了本地部署与容器化部署的优势。通过官方镜像和Docker Compose两种方式,5分钟即可完成部署,并详细讲解了配置管理方案(挂载配置文件和环境变量)。文章还提供了飞书集成配置方法,以及生产环境下的日志管理、资源限制、健康检查等优化建议。最后包含常见问题排查指南,帮助开发者快速实现OpenClaw的容器化部署。

刘一说的IT专栏 904

HTTP Basic/Digest Authentication、OAuth

HTTP Authentication [code] auth-scheme = token auth-param = token "=" ( token | quoted-string ) challenge = auth-scheme 1*SP 1#auth-param [/code] The 401 (Unautho...

hideto 394

《信息化项目文档模板十二——业务需求新增/变更审批确认表 》

系列文章目录 《信息化项目文档模板一——项目需求说明书》 《信息化项目文档模板二——项目启动会文档模板》 《信息化项目文档模板三——会议纪要模板》 《信息化项目文档模板四——系统项目蓝图设计模板》 《信息化项目文档模板五——系统详细设计模板》 《信息化项目文档模板六——系统详细设计模板》 《信息化项目文档模板七——系统开发计划模板》 《信息化项目文档模板八——系统功能测试模板》 《信息化项目文档模板九——系统压力测试模板》 《信息化项目文档模板十——系统推广上线计划模板》 《信息化项目文档模板十一——系统用

商务合作|问题讨论|交流学习 请联系作者微信,加微信请务必注明来意,博客主页有联系方式 1712

数学建模模型总结

这是本人在两年内准备参加数学建模竞赛搜集到的模型资料,已经经过了本人的筛选和整理,希望能够对准备参加数学建模竞赛的学弟学妹们提供一些帮助!

以后都用MindManager做年度总结和年度计划

2008总结如下: [img]/upload/attachment/61388/ee893292-54b3-3f26-b057-e8fada2a0d4a.jpeg[/img] 2009计划如下: [img]/upload/attachment/61390/08b2f845-c927-35ca-8bf2-b5ebdfeeeb17.jpeg[/img] 希望自己能够戒骄躁,深研究,多进步...

hideto 315

OV9734 DATASHEET,完整规格书

OV9734完整规格书,包括电气参数,尺寸规格,寄存器配置表等

HTTP1.1 Notes 4, Request & Response & Entity

[color=blue][b]Request[/b][/color] Request = Request-Line *(( general-header | request-header ...

hideto 224

ssm框架搭建

这个是一个在idea上成功跑起来的ssm框架项目,保存在这里方便以后使用直接下载

ET2012新版免狗免安装绿色软件

ET2012新版免狗免安祖昂绿色软件。,新界面,新视觉,

DyberPet 与 VPet 对比评测:2款开源桌宠框架在功能、性能与生态上的差异

本文深入对比了开源桌宠框架DyberPet(基于Unity)与VPet(基于WPF)在技术架构、功能实现、性能表现及社区生态等方面的差异。DyberPet凭借Unity引擎支持复杂动画与跨平台能力,适合游戏开发场景;VPet则以其轻量化与Windows深度集成优势,更适合办公辅助应用。文章为开发者提供了详细的技术选型指南与性能优化建议。

hideto 219

Skip List 跳表

跳表是个概率性的的数据结构,由William Pugh在1990年发明,列表基于平行的链接列表,效率相对二叉搜索树(对于大多数操作平均需要O(log n)时间)有显著改善 例子: [code] 1 1-----4---6 1---3-4---6-----9 1-2-3-4-5-6-7-8-9-10 [/code] 最底层为所有排好序的元素组成的链表 次底层为按概率1/p组...

hideto 196

数据仓库toolkit笔记1,Dimensional Modeling Primer

[b]数据仓库管理员的主要职责:[/b] 1,通过业务领域、工作职责和计算机能力来理解用户 2,通过数据仓库来确定业务用户所需要做的决定 3,使用数据仓库区分最好的用户:制定高效的、大影响力的决定的用户 4,找到潜在的新用户并让它们了解数据仓库 5,选择最有效、最易操作的数据子集到数据仓库,而不是将汪洋大海般的数据都弄过来 6,使得用户界面和应用简单、模板化,特别是匹配用户的认知和理解...

hideto 187

CLRS笔记10、基本数据结构

数学中的集合是不变的,而算法所操作的集合是可以增大、缩小或产生其他变化的,称这种集合为动态集合 支持插入元素、删除元素和测试元素是否属于集合操作的动态集合称为字典 [b]栈和队列[/b] 栈为后进先出LIFO,队列为先进先出FIFO 栈的INSERT操作称为PUSH,DELETE操作成为POP 队列的INSERT操作称为ENQUEUE,DELETE操作称为DEQUEUE [b]...

hideto 182
上一篇: HTTP1.1 Notes 7, Status Code Definitions
下一篇: 在FreeWheel一年半的小结
hidetobj
博客等级 码龄19年 16粉丝 301原创
评论
成就一亿技术人!
拼手气红包6.0元
还能输入1000个字符
 
 条评论被折叠 查看
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付:10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值