<?xml version="1.0" encoding="UTF-8"?>
<xliff xmlns="urn:oasis:names:tc:xliff:document:1.1" version="1.1">
  <file original="NoName" source-language="en" datatype="plaintext" target-language="en">
    <body>
      <trans-unit xml:space="preserve" approved="no" id="3e10e202825b1fc4" weblate-flags="read-only">
        <source>Custom Parsers</source>
        <target state="translated">Custom Parsers</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">10</context>
        </context-group>
        <note from="developer">type: section title</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="ad1a1442a38251e5" weblate-flags="read-only">
        <source>While the parsers included in the library will handle a broad number of use-cases, the __basic_parser__ interface can be subclassed to implement custom strategies for storing parsed results: the basic parser processes input buffers into elements according to the HTTP/1 protocol specification, while the derived class decides what to do with those elements. Custom parsers will work with all of the HTTP stream read algorithms, as those algorithms use only the basic parser interface. Some use cases for implementing custom parsers are:</source>
        <target state="translated">While the parsers included in the library will handle a broad number of use-cases, the __basic_parser__ interface can be subclassed to implement custom strategies for storing parsed results: the basic parser processes input buffers into elements according to the HTTP/1 protocol specification, while the derived class decides what to do with those elements. Custom parsers will work with all of the HTTP stream read algorithms, as those algorithms use only the basic parser interface. Some use cases for implementing custom parsers are:</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">12</context>
        </context-group>
        <note from="developer">type: paragraph</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="fc19defcc7c6ad0e" weblate-flags="read-only">
        <source>* Inspect incoming header fields and keep or discard them.</source>
        <target state="translated">* Inspect incoming header fields and keep or discard them.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">21</context>
        </context-group>
        <note from="developer">type: list</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="2a56991d20adb251" weblate-flags="read-only">
        <source>* Use a container provided by an external interface.</source>
        <target state="translated">* Use a container provided by an external interface.</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">23</context>
        </context-group>
        <note from="developer">type: list</note>
      </trans-unit>
      <trans-unit xml:space="preserve" approved="no" id="5209242f2db1859a" weblate-flags="read-only">
        <source>The basic parser uses virtual functions. To declare your user-defined parser, derive from __basic_parser__ and implement all the required virtual functions. A declaration for the derived class may look like this:</source>
        <target state="translated">The basic parser uses virtual functions. To declare your user-defined parser, derive from __basic_parser__ and implement all the required virtual functions. A declaration for the derived class may look like this:</target>
        <context-group name="" purpose="location">
          <context context-type="sourcefile">25</context>
        </context-group>
        <note from="developer">type: paragraph</note>
      </trans-unit>
    </body>
  </file>
</xliff>
