| 1 |
Source: fstrm |
| 2 |
Section: libs |
| 3 |
Priority: optional |
| 4 |
Maintainer: Robert Edmonds <[email protected]> |
| 5 |
Build-Depends: |
| 6 |
, debhelper-compat (= 13) |
| 7 |
, pkg-config |
| 8 |
, libevent-dev |
| 9 |
Standards-Version: 4.6.0 |
| 10 |
Homepage: https://github.com/farsightsec/fstrm |
| 11 |
Vcs-Browser: https://salsa.debian.org/edmonds/fstrm |
| 12 |
Vcs-Git: https://salsa.debian.org/edmonds/fstrm.git |
| 13 |
|
| 14 |
Package: libfstrm0 |
| 15 |
Architecture: any |
| 16 |
Depends: ${misc:Depends}, ${shlibs:Depends} |
| 17 |
Pre-Depends: ${misc:Pre-Depends} |
| 18 |
Multi-Arch: same |
| 19 |
Description: Frame Streams (fstrm) library |
| 20 |
Frame Streams is a light weight, binary clean protocol that allows for the |
| 21 |
transport of arbitrarily encoded data payload sequences with minimal framing |
| 22 |
overhead -- just four bytes per data frame. Frame Streams does not specify an |
| 23 |
encoding format for data frames and can be used with any data serialization |
| 24 |
format that produces byte sequences, such as Protocol Buffers, XML, JSON, |
| 25 |
MessagePack, YAML, etc. Frame Streams can be used as both a streaming |
| 26 |
transport over a reliable byte stream socket (TCP sockets, TLS connections, |
| 27 |
AF_UNIX sockets, etc.) for data in motion as well as a file format for data |
| 28 |
at rest. A "Content Type" header identifies the type of payload being carried |
| 29 |
over an individual Frame Stream and allows cooperating programs to determine |
| 30 |
how to interpret a given sequence of data payloads. |
| 31 |
. |
| 32 |
This is the "fstrm" implementation of Frame Streams in C. |
| 33 |
. |
| 34 |
This package contains the shared library. |
| 35 |
|
| 36 |
Package: libfstrm-dev |
| 37 |
Section: libdevel |
| 38 |
Architecture: any |
| 39 |
Depends: ${misc:Depends}, libfstrm0 (= ${binary:Version}) |
| 40 |
Multi-Arch: same |
| 41 |
Description: Frame Streams (fstrm) library (development files) |
| 42 |
Frame Streams is a light weight, binary clean protocol that allows for the |
| 43 |
transport of arbitrarily encoded data payload sequences with minimal framing |
| 44 |
overhead -- just four bytes per data frame. Frame Streams does not specify an |
| 45 |
encoding format for data frames and can be used with any data serialization |
| 46 |
format that produces byte sequences, such as Protocol Buffers, XML, JSON, |
| 47 |
MessagePack, YAML, etc. Frame Streams can be used as both a streaming |
| 48 |
transport over a reliable byte stream socket (TCP sockets, TLS connections, |
| 49 |
AF_UNIX sockets, etc.) for data in motion as well as a file format for data |
| 50 |
at rest. A "Content Type" header identifies the type of payload being carried |
| 51 |
over an individual Frame Stream and allows cooperating programs to determine |
| 52 |
how to interpret a given sequence of data payloads. |
| 53 |
. |
| 54 |
This is the "fstrm" implementation of Frame Streams in C. |
| 55 |
. |
| 56 |
This package contains the static library and development headers. |
| 57 |
|
| 58 |
Package: fstrm-bin |
| 59 |
Section: utils |
| 60 |
Architecture: any |
| 61 |
Depends: ${misc:Depends}, ${shlibs:Depends} |
| 62 |
Description: Frame Streams (fstrm) library (utilities) |
| 63 |
Frame Streams is a light weight, binary clean protocol that allows for the |
| 64 |
transport of arbitrarily encoded data payload sequences with minimal framing |
| 65 |
overhead -- just four bytes per data frame. Frame Streams does not specify an |
| 66 |
encoding format for data frames and can be used with any data serialization |
| 67 |
format that produces byte sequences, such as Protocol Buffers, XML, JSON, |
| 68 |
MessagePack, YAML, etc. Frame Streams can be used as both a streaming |
| 69 |
transport over a reliable byte stream socket (TCP sockets, TLS connections, |
| 70 |
AF_UNIX sockets, etc.) for data in motion as well as a file format for data |
| 71 |
at rest. A "Content Type" header identifies the type of payload being carried |
| 72 |
over an individual Frame Stream and allows cooperating programs to determine |
| 73 |
how to interpret a given sequence of data payloads. |
| 74 |
. |
| 75 |
This is the "fstrm" implementation of Frame Streams in C. |
| 76 |
. |
| 77 |
This package contains the command line utilities. |