Etienne CHAMPETIER d33d8b87e4 ChannelData: rework padding
getDataLength() was returning data length without
padding, so keep current behavior and update the javadoc.
(spotted with findbugs because length in
getDataLength was a dead store)

Introduce padTo4() to round up a number to the next
multiple of 4.

Deprecate encode() and introduce encode(boolean pad)
so we can let the caller decide if he wants padding
(mandatory when using tcp or tls)

See https://tools.ietf.org/html/rfc5766#section-11.5

Signed-off-by: Etienne CHAMPETIER <champetier.etienne@gmail.com>
2016-05-03 11:25:03 +02:00
2016-04-02 15:01:37 +02:00
2016-05-03 11:25:03 +02:00
2015-09-07 17:36:03 +02:00

ice4j

The Interactive Connectivity Establishment (ICE) protocol combines various NAT traversal utilities such as the STUN and TURN protocols in order to offer a powerful mechanism that allows Offer/Answer based protocols such as SIP and XMPP to traverse NATs.

This project provides a Java implementation of the ICE protocol that would be usable by both SIP and XMPP applications. The project also provides features such as socket sharing and support for Pseudo TCP.

ice4j is maintained by the Jitsi community. Use Jitsi's dev mailing list for questions and discussions.

Thanks

Work on this project was graciously funded by the NLnet Foundation. Thank you!

Description
A Java implementation of the ICE protocol
Readme 6.2 MiB
Languages
Java 98.6%
Kotlin 1.4%