A very efficient and flexible message protocol designed for close-to-the-wire transactions. https://wireproto.io/
Go to file
brent saner 9b39811206
v1.0.1
FIX:
* Cleaned up some documentation
2024-07-10 00:40:12 -04:00
.githooks/pre-commit v1.0.0 2024-07-10 00:18:54 -04:00
.gitignore v1.0.0 2024-07-10 00:18:54 -04:00
consts.go v1.0.1 2024-07-10 00:40:12 -04:00
doc.go v1.0.0 2024-07-10 00:18:54 -04:00
errs.go v1.0.0 2024-07-10 00:18:54 -04:00
funcs_fieldname.go v1.0.0 2024-07-10 00:18:54 -04:00
funcs_fieldvalue.go v1.0.0 2024-07-10 00:18:54 -04:00
funcs_fieldvaluepair.go v1.0.0 2024-07-10 00:18:54 -04:00
funcs_request.go v1.0.1 2024-07-10 00:40:12 -04:00
funcs_requestrecord.go v1.0.1 2024-07-10 00:40:12 -04:00
funcs_requestrecordgroup.go v1.0.1 2024-07-10 00:40:12 -04:00
funcs_response.go v1.0.1 2024-07-10 00:40:12 -04:00
funcs_responserecord.go v1.0.0 2024-07-10 00:18:54 -04:00
funcs_responserecordgroup.go v1.0.1 2024-07-10 00:40:12 -04:00
funcs_test.go v1.0.0 2024-07-10 00:18:54 -04:00
funcs.go v1.0.0 2024-07-10 00:18:54 -04:00
go.mod v1.0.0 2024-07-10 00:18:54 -04:00
go.sum v1.0.0 2024-07-10 00:18:54 -04:00
LICENSE v1.0.0 2024-07-10 00:18:54 -04:00
README.adoc v1.0.1 2024-07-10 00:40:12 -04:00
README.html v1.0.1 2024-07-10 00:40:12 -04:00
test_obj_multi_req.go v1.0.0 2024-07-10 00:18:54 -04:00
test_obj_multi_resp.go v1.0.0 2024-07-10 00:18:54 -04:00
test_obj_simple_req.go v1.0.0 2024-07-10 00:18:54 -04:00
test_obj_simple_resp.go v1.0.0 2024-07-10 00:18:54 -04:00
types.go v1.0.0 2024-07-10 00:18:54 -04:00

<html lang="en"> <head> </head>

Go WireProto API Documentation

Brent Saner
bts@square-r00t.net
Last rendered 2024-07-10 00:40:13 -0400
Table of Contents

1. Reference

In addition to the documentation found in this document and the specification, library usage documentation can be found at the Golang module documentation page:

Go Reference

2. License

This library is licensed for use, inclusion, and distribution under the "3-Clause BSD" license.

Full License
Copyright (c) 2024 Brent Saner (r00t^2). 

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. Neither the name of the copyright holder nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

3. TODO

The following are a wishlist or things planned that may come in later versions.

  • More clear errors

    • Currently during e.g. UnmarshalBinary calls, just an io.EOF will be returned if the buffer is exhausted early. This may be able to be a little more context-helpful by using the Err* errors.

  • Confirmation of read/write sizes in buffers

    • The sizes they should be are known, theres no reason to not confirm it.

  • Goroutines

    • This of course wont work for serializing and keeping order of children (e.g. RG ⇒ Record); thatd still need to be ordered, but it will allow for parallel parsing of those children. Should benchmark, though; it may not be worth it.

  • context.Context support for Read* and Write* funcs

    • This is a relatively low priority as the passed net.Conn will likely return an error if its own context is canceled. This can be handled in the caller downstream.

</html>