Development |
Development.TransportInterface HistoryHide minor edits - Show changes to markup December 19, 2014, at 12:51 PM
by
- Changed lines 13-14 from:
In order to simplify this, we designed a new Transport Interface that aims to provide a new transport layer in OpenSIPS's core. This interface facilitates the addition of higher level protocols (such as TLS, WebSocket, SCTP) while reusing the lower level protocols implementations (such as TCP and UDP). to:
In order to simplify this, we designed a new Transport Interface that aims to provide a new transport layer in OpenSIPS's core. This interface will separate the network level transport protocols (such as TCP and UDP) from higher level, SIP aware, protocols (such as TLS, WebSocket, SCTP). This clear separation will facilitate the addition of higher level protocols while efficiently reusing the lower network level protocols implementations. Changed lines 22-23 from:
to:
December 19, 2014, at 12:04 PM
by
- Changed lines 17-24 from:
to:
The architecture of the new Transport Interface is presented in the picture below.
The picture can be split in three layers, from bottom up:
December 10, 2014, at 06:14 PM
by
- Changed line 17 from:
http://opensips.org/images/opensips-transport-interface.png to:
December 10, 2014, at 06:14 PM
by
- Changed lines 15-17 from:
Designto:
Designhttp://opensips.org/images/opensips-transport-interface.png December 10, 2014, at 05:26 PM
by
- Added lines 1-15:
DescriptionThe current transport protocols (UDP, TCP, TLS, etc.) are embedded directly in the OpenSIPS core. This makes the management of these protocols in script more difficult and also complicates the addition of new ones (such as WebSockets). In order to simplify this, we designed a new Transport Interface that aims to provide a new transport layer in OpenSIPS's core. This interface facilitates the addition of higher level protocols (such as TLS, WebSocket, SCTP) while reusing the lower level protocols implementations (such as TCP and UDP). Design |