Bug#993666: ITP: golang-github-davecgh-go-xdr -- Implements the XDR standard as specified in RFC 4506 in pure Go (Golang)
Package: wnpp
Severity: wishlist
Owner: John Goerzen <jgoerzen@complete.org>
* Package name : golang-github-davecgh-go-xdr
Version : 0.0~git20161123.e6a2ba0-1
Upstream Author : Dave Collins
* URL : https://github.com/davecgh/go-xdr
* License : ISC
Programming Lang: Go
Description : Implements the XDR standard as specified in RFC 4506 in pure Go (Golang)
go-xdr Build Status (https://travis-ci.org/davecgh/go-xdr) Coverage Status
(https://coveralls.io/r/davecgh/go-xdr?branch=master)
.
Go-xdr implements the data representation portion of the External Data
Representation (XDR) standard protocol as specified in RFC 4506 (obsoletes
RFC 1832 and RFC 1014) in Pure Go (Golang). A comprehensive suite of
tests are provided to ensure proper functionality. It is licensed under
the liberal ISC license, so it may be used in open source or commercial
projects.
.
NOTE: Version 1 of this package is still available via the
github.com/davecgh/go-xdr/xdr import path to avoid breaking existing
clients. However, it is highly recommended that all old clients
upgrade to version 2 and all new clients use version 2. In addition
to some speed optimizations, version 2 has been been updated to
work with standard the io.Reader and io.Writer interfaces instead of
raw byte slices. This allows it to be much more flexible and work
directly with files, network connections, etc. Documentation GoDoc
(http://godoc.org/github.com/davecgh/go-xdr/xdr2)
.
Full go doc style documentation for the project can be viewed online
without installing this package by using the excellent GoDoc site here:
http://godoc.org/github.com/davecgh/go-xdr/xdr2
.
You can also view the documentation locally once the package is installed
with the godoc tool by running godoc -http=":6060" and pointing your
browser to http://localhost:6060/pkg/github.com/davecgh/go-xdr/xdr2/
Installation bash $ go get github.com/davecgh/go-xdr/xdr2
.
Required for packaging NNCP
Reply to: