pkg/oonf_api: use new repo url#5111
Merged
cgundogan merged 1 commit intoRIOT-OS:masterfrom Mar 19, 2016
Merged
Conversation
cgundogan
added
Type: bug
OlegHahm
added
the
CI: ready for build
Member
|
If the CIs agree, I would say ACK. |
Member
Author
|
both CIs agree - GO |
cgundogan
added a commit
that referenced
this pull request
Mar 19, 2016
pkg/oonf_api: use new repo url
miri64
added a commit
to miri64/RIOT
that referenced
this pull request
Jun 8, 2016
This change overhauls the `conn` API in the following manner: * for every `conn` objects now also one can add a callback for asynchronous reception on creation * The source address on creation may now be `NULL`, implying an implicit bind when sending. This makes the `conn_find_best_source()` function unnecessary. * a common address type for both IPv4 and IPv6 addresses was introduced * instead of having addresses, address length and ports/protocols given separately a new data type called "end points" for every connectivity type is introduced `conn_ep_x_t`, consisting of the address, its family, an (optional) interface identifier (see RIOT-OS#5111) and its port/protocol * send for connection-less communication was simplified by not requiring source information anymore (a stack is encouraged to find a best match itself). It and the interface one is supposed to send over can however be supplied by (optionally) providing an already created `conn` object * TCP connection establishment was simplified: listen/connect functions were dropped, instead a user can either give the remote end point on creation (implicit connect) or omit it (implicit listen)
miri64
added a commit
to miri64/RIOT
that referenced
this pull request
Jun 8, 2016
This change overhauls the `conn` API in the following manner: * for every `conn` objects now also one can add a callback for asynchronous reception on creation * The source address on creation may now be `NULL`, implying an implicit bind when sending. This makes the `conn_find_best_source()` function unnecessary. * a common address type for both IPv4 and IPv6 addresses was introduced * instead of having addresses, address length and ports/protocols given separately a new data type called "end points" for every connectivity type is introduced `conn_ep_x_t`, consisting of the address, its family, an (optional) interface identifier (see RIOT-OS#5111) and its port/protocol * send for connection-less communication was simplified by not requiring source information anymore (a stack is encouraged to find a best match itself). It and the interface one is supposed to send over can however be supplied by (optionally) providing an already created `conn` object * TCP connection establishment was simplified: listen/connect functions were dropped, instead a user can either give the remote end point on creation (implicit connect) or omit it (implicit listen)
miri64
added a commit
to miri64/RIOT
that referenced
this pull request
Jun 8, 2016
This change overhauls the `conn` API in the following manner: * for every `conn` objects now also one can add a callback for asynchronous reception on creation * The source address on creation may now be `NULL`, implying an implicit bind when sending. This makes the `conn_find_best_source()` function unnecessary. * a common address type for both IPv4 and IPv6 addresses was introduced * instead of having addresses, address length and ports/protocols given separately a new data type called "end points" for every connectivity type is introduced `conn_ep_x_t`, consisting of the address, its family, an (optional) interface identifier (see RIOT-OS#5111) and its port/protocol * send for connection-less communication was simplified by not requiring source information anymore (a stack is encouraged to find a best match itself). It and the interface one is supposed to send over can however be supplied by (optionally) providing an already created `conn` object * TCP connection establishment was simplified: listen/connect functions were dropped, instead a user can either give the remote end point on creation (implicit connect) or omit it (implicit listen)
miri64
added a commit
to miri64/RIOT
that referenced
this pull request
Jun 8, 2016
This change overhauls the `conn` API in the following manner: * for every `conn` objects now also one can add a callback for asynchronous reception on creation * The source address on creation may now be `NULL`, implying an implicit bind when sending. This makes the `conn_find_best_source()` function unnecessary. * a common address type for both IPv4 and IPv6 addresses was introduced * instead of having addresses, address length and ports/protocols given separately a new data type called "end points" for every connectivity type is introduced `conn_ep_x_t`, consisting of the address, its family, an (optional) interface identifier (see RIOT-OS#5111) and its port/protocol * send for connection-less communication was simplified by not requiring source information anymore (a stack is encouraged to find a best match itself). It and the interface one is supposed to send over can however be supplied by (optionally) providing an already created `conn` object * TCP connection establishment was simplified: listen/connect functions were dropped, instead a user can either give the remote end point on creation (implicit connect) or omit it (implicit listen)
miri64
added a commit
to miri64/RIOT
that referenced
this pull request
Aug 5, 2016
This change overhauls the `conn` API in the following manner: * for every `conn` objects now also one can add a callback for asynchronous reception on creation * The source address on creation may now be `NULL`, implying an implicit bind when sending. This makes the `conn_find_best_source()` function unnecessary. * a common address type for both IPv4 and IPv6 addresses was introduced * instead of having addresses, address length and ports/protocols given separately a new data type called "end points" for every connectivity type is introduced `conn_ep_x_t`, consisting of the address, its family, an (optional) interface identifier (see RIOT-OS#5111) and its port/protocol * send for connection-less communication was simplified by not requiring source information anymore (a stack is encouraged to find a best match itself). It and the interface one is supposed to send over can however be supplied by (optionally) providing an already created `conn` object * TCP connection establishment was simplified: listen/connect functions were dropped, instead a user can either give the remote end point on creation (implicit connect) or omit it (implicit listen)
miri64
added a commit
to miri64/RIOT
that referenced
this pull request
Aug 11, 2016
This change overhauls the `conn` API in the following manner: * The source address on creation may now be `NULL`, implying an implicit bind when sending. This makes the `conn_find_best_source()` function unnecessary. * a common address type for both IPv4 and IPv6 addresses was introduced * instead of having addresses, address length and ports/protocols given separately a new data type called "end points" for every connectivity type is introduced `conn_ep_x_t`, consisting of the address, its family, an (optional) interface identifier (see RIOT-OS#5111) and its port/protocol * send for connection-less communication was simplified by not requiring source information anymore (a stack is encouraged to find a best match itself). It and the interface one is supposed to send over can however be supplied by (optionally) providing an already created `conn` object * TCP connection establishment was simplified: listen/connect functions were dropped, instead a user can either give the remote end point on creation (implicit connect) or omit it (implicit listen)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fixes #5107
apparently they moved to github [1].
[1] https://lists.olsr.org/pipermail/olsr-dev/2016-March/008182.html