{
    "content": [
        {
            "type": "text",
            "text": "# Net::SSH::Buffer (ri)\n\n## Sections\n\n- **Net::SSH::Buffer < Object**\n- **Class methods:**\n- **Instance methods:**\n- **Attributes:**\n\nUse structuredContent.sections for detailed options, examples, and full documentation.\n"
        }
    ],
    "structuredContent": {
        "command": "Net::SSH::Buffer",
        "section": "",
        "mode": "ri",
        "summary": null,
        "synopsis": null,
        "tldr_summary": null,
        "tldr_examples": [],
        "tldr_source": null,
        "flags": [],
        "examples": [],
        "see_also": [],
        "section_outline": [
            {
                "name": "Net::SSH::Buffer < Object",
                "lines": 17,
                "subsections": []
            },
            {
                "name": "Class methods:",
                "lines": 3,
                "subsections": []
            },
            {
                "name": "Instance methods:",
                "lines": 38,
                "subsections": []
            },
            {
                "name": "Attributes:",
                "lines": 3,
                "subsections": []
            }
        ],
        "sections": {
            "Net::SSH::Buffer < Object": {
                "content": "(from /home/chedong/.local/share/rdoc)\n------------------------------------------------------------------------\nNet::SSH::Buffer is a flexible class for building and parsing binary\ndata packets. It provides a stream-like interface for sequentially\nreading data items from the buffer, as well as a useful helper method\nfor building binary packets given a signature.\n\nWriting to a buffer always appends to the end, regardless of where the\nread cursor is. Reading, on the other hand, always begins at the first\nbyte of the buffer and increments the read cursor, with subsequent reads\ntaking up where the last left off.\n\nAs a consumer of the Net::SSH library, you will rarely come into contact\nwith these buffer objects directly, but it could happen. Also, if you\nare ever implementing a protocol on top of SSH (e.g. SFTP), this buffer\nclass can be quite handy.\n------------------------------------------------------------------------",
                "subsections": []
            },
            "Class methods:": {
                "content": "from\nnew\n",
                "subsections": []
            },
            "Instance methods:": {
                "content": "==\nappend\navailable\nclear!\nconsume!\ncontent\nempty?\neof?\nlength\nposition\nread\nread!\nreadall\nreadbignum\nreadbool\nreadbuffer\nreadbyte\nreadint64\nreadkey\nreadkeyblob\nreadlong\nreadprivatekeyblob\nreadstring\nreadto\nremainderasbuffer\nreset!\ntos\nwrite\nwritebignum\nwritebool\nwritebyte\nwriteint64\nwritekey\nwritelong\nwritemoved\nwritemstring\nwritestring\n",
                "subsections": []
            },
            "Attributes:": {
                "content": "attraccessor position\nattrreader content\n",
                "subsections": []
            }
        }
    }
}