英语释义

1. radio-frequency choke

片语

rfc algorithmrfc算法

RFC RequestForComments请求看备注

Tournai RFC图尔奈

dokument RFC要求建议

RFC Meux梅克斯

RFC RadioFrequencyConverter射频转换器

IETF RFC同时也增加了对网络工程任务组制订标準

Transcation RFC事务性RFC

英汉例句

• The SIP RFC defines two types of Proxy Servers, one stateful and one stateless.

  SIPRFC定义了两种类型的代理服务器，有状态代理服务器和无状态代理服务器。

• The current standard for digital certificates is X.509, as defined in RFC 3280.

  目前数字证书所采用的标準是X . 509，这是在RFC 3280中定义的。

• RFC 2397 (see Resources) defines a special URI type where the resource data is all contained within the URI itself.

  RFC 2397(请参见参考资料)定义了一个特殊的uri类型，其中资源数据都包含到了URI本身中。

• The difference is described in part 4 of RFC 2396, but the best practice is to use ordinary URIs.

  RFC 2396 第 4部分描述了两者的差异，但最佳实践是使用普通URI。

• The RFC moves on to coverage of content constructs with sections 4.5 and 4.6, which offer very sensible advice on when to use processing instructions and comments.

  RFC在4.5和4.6节讨论内容结构，就何时使用处理指令和注释提供了非常合理的建议。

• The first approach is to use the regular expressions defined in RFC 4627 to make sure the JSON data doesn「t contain active parts.

  第一个方法是使用RFC 4627中所定义的正则表达式确保JSON数据中不包含活动的部分。

• In addition to providing broad exposure, the draft proposed standard captured in the RFC lays a firm foundation for actual product development.

  除了对公众公开以外，这个草案采用的RFC标準为实际产品开发打下坚实的基础。

• The element produces a timestamp (compliant with the RFC 3339 standard) that tells the consumer of this feed when it was last updated.

  元素生成一个时间戳（符合RFC 3339标準）并告知此提要的用户它最后一次被更新的时间。

• It was developed by the GNU project and standardized by RFC 1952.

  它是由GNU项目开发，并由RFC 1952规范。

• The problem is specifically in a mismatch between the RFC 3986 form of URIs and the more 「popular」 attachment to the path component of URIs.

  具体地说，RFC 3986形式的uri与uri路径成分的「常用」附件之间不匹配。

• RFC 1766 is an Internet standard which defines the tag for the identification of languages.

  RFC 1766是一个因特网标準，它定义用来标识语言的标记。

• Invoking the BAPI outbound interfaces is actually making a RFC call on that module to perform some function within SAP.

  调用BAPI出站接口实际上是对这个模块执行rfc调用，从而在SAP中执行某个函数。

• Besides the attributes defined in RFC 2307, AIX also has additional attributes to support extended AIX user functionality.

  除了在RFC 2307中定义的属性之外，AIX还提供了一些附加的属性以支持扩展的AIX用户功能。

• When published, the formal RFC review period often lasts a year.

  发布之后，RFC的正式审核期是一年。

• According to RFC 2253, a DN is written as a comma-separated list of components, with each component having its value.

  根据RFC 2253,DN是用逗号分隔的组件列表的形式编写的，每个组件都有自己的值。

• The next two lines retrieve the article date (from the POSTED column) and convert it to RFC 3339 format using the aforementioned function.

  接下来的两行代码检索文章日期(从posted列)并使用之前提到的函数将其转变为RFC 3339格式。

• That is a custom-built PHP function that produces a timestamp in RFC 3339 format.

  这是一个定制的PHP函数，可以生成RFC 3339格式的时间戳。

• RFC 2307 defines a standard set of schema for Network Information Services (NIS), which covers users, groups, and other NIS objects.

  RFC 2307定义了网络信息服务(NIS)模式的标準集合，其中包括用户、组和其他的NIS对象。

• Check create RFC destination automatically, and select Yes on the pop-up asking if you want to create the names automatically.

  自动检查Createrfc目的地，并在询问您是否想自动创建名称的弹出窗口上选择Yes。

• Details on how this attack works are explained in IETF RFC 2965, if you」re curious (see Resources for a link).

  如果您对此关心，可以参考IETFRFC 2965，可以得到关于这种攻击的详细说明(在参考资料中有相关链接)。

• For more information on attribute syntax types refer to RFC 2252.

  有关属性语法类型的详细信息，请参阅rfc 2252。

• In RFC 3262, a mechanism was developed to ensure that the responses are sent reliably and acknowledged alone so that the status of the call is not lost if the transport protocol is something like UDP.

  在RFC 3262中，开发了一项机制来确保可靠地发送消息，且仅为确认目的而发送，以便在使用udp之类的传输协议时不会丢失呼叫状态。

• Although URI schemes are case insensitive, the tag RFC (see Resources) recommends the lower-case form.

  虽然uri方案对大小写不敏感，但是标签RFC(请参阅参考资料)建议采用小写形式。

• While using the RFC 3339 serialization requires additional work, it is the only option that avoids data loss and ambiguity.

  尽管使用RFC 3339序列需要额外的工作，但这是避免数据丢失和数据含义不明的惟一选项。

• RFC 2253 (see Resources) provides the syntax to write a DN in the form of a string.

  RFC 2253(请参阅参考资料)提供了以字符串形式编写DN的语法。

• One possible reason for not doing so is hinted at in RFC 3470.

  RFC 3470中给出了不这样做的一个理由。