otp.git - Mirror of Erlang/OTP repository.

Age	Commit message (Collapse)	Author
2016-03-15	update copyright-year	Henrik Nord

2015-06-18	Change license text to APLv2	Bruce Yinhe

2014-01-27	Merge branch 'anders/diameter/sctp_streams/OTP-11593'	Anders Svensson
	* anders/diameter/sctp_streams/OTP-11593: Change interface for communicating outbound stream id to diameter_sctp
2014-01-24	Change interface for communicating outbound stream id to diameter_sctp	Anders Svensson
	The module uses the transport_data field of record diameter_packet to communicate the stream on which the an incoming message is received and on which an outgoing message should be sent, the previous interface being that both are communicated as a tuple of the form {stream, Id}. However, since diameter retains the value of an incoming request's transport_data unless the corresponding answer message specifies otherwise, the behaviour in this case is to send an answer on the outbound stream with the same identifier as the that of the inbound stream on which the request was received. If the inbound stream id is greater than or equal to the number of outbound streams then this is guaranteed to fail, causing the transport process in question to terminate. There is no relationship between inbound and outbound stream identifiers so diameter_sctp's imposition of one is simply wrong. Outbound stream ids are now communicated with a different tuple: {outstream, Id}, interpreted modulo the number of outbound streams. Thus, retention of an inbound request's transport_data has no effect on the selection of an outbound stream. The change in interface is not strictly backwards compatible because of the new atom for the outbound stream. However, as there is currently no documented way of obtaining the available number of outbound streams for a peer connection, there is no way for a client to have known the range of ids from which it could reliably have chosen with the previous interface, so any setting of the outbound stream has probably been unintentional. Not explicitly specifying an outbound stream now results in a round-robin selection.
2013-12-02	Merge branch 'maint'	Anders Svensson

2013-11-29	Fix documentation typos	Anders Svensson

2013-06-11	Merge branch 'maint'	Anders Svensson

2013-06-10	Let diameter_{tcp,sctp} be configured with permissible remote addresses	Anders Svensson
	Option 'accept' allows remote addresses to be configured as tuples or regular expressions. The remote addresses for any incoming (aka accepted) connection/association are matched against the configured values, any non-matching address causing the connection/association to be aborted.
2013-04-19	Convert XML files to UTF-8	Hans Bolinder

2013-02-10	Simplify and document diameter_tcp fragment timer	Anders Svensson
	Don't start a new timer with each incoming message. Instead, start a timer at timeout and flush after two successive timeouts with no message reception.
2012-11-22	Add content to diameter_codec(3) and diameter_make(3)	Anders Svensson

2012-11-18	Generate intra-document references	Anders Svensson

2012-11-18	Use entities for cross references	Anders Svensson

2012-11-15	Minor doc fixes	Anders Svensson
	Presentation (order, cross-references), not content.
2012-08-30	Fix/tweak references to other applications	Anders Svensson

2012-08-29	Add SCTP warning, more references	Anders Svensson

2012-08-29	Terminology and other clarifications, more references	Anders Svensson
	Diameter node/peer having been the most vicious terminology blunder.
2011-09-26	Minor documentation fixes	Anders Svensson
	Connector/listener -> connecting/listening transport.
2011-05-18	Initial commit of the diameter application.	Anders Svensson
	The application provides an implementation of the Diameter protocol as defined in RFC 3588.