| Author | SHA1 | Message | Date |
|---|---|---|---|
|
|
d64c888a0e |
TT#36301 transcoding unit tests
Change-Id: If48e5afe5a343b557183b6e87441f52424dd2c6a |
8 years ago |
|
|
75056a8dd1 |
eliminate the callmaster struct
Change-Id: I9151dbe8f47b3bb9ab67d6fea2fc3783bdc558da |
8 years ago |
|
|
d10952a029 |
TT#26757 add tcp_listener framework
Change-Id: I402d36637235ba0cc03e77d426f4dd9cbc4722a9 |
8 years ago |
|
|
6d3865b971 |
Mass update - manual merge of rfuchs/socket-rework branch
This brings master up to date with branch `rfuchs/socket-rework` at commit `b1bcc096b7`. The branches have diverged too much for a proper merge, so this is a manual (squashed) merge. The old master before this merge can be found in branch `old-master-before-socket-rework` (commit `82199216b2`). This is a complete rewrite of all socket handling routines. The most important functional change is that sockets aren't indiscriminately bound to INADDR_ANY (or rather in6addr_any), but instead are always bound to their respective local interface address and with the correct address family. Side effects of this are that in multi-homed environments, multiple sockets must be opened (one per interface address and family) which must be taken into account when considering RLIMIT_NOFILE values. As a benefit, this change allows rtpengine to utilize the full UDP port space per interface address, instead of just one port space per machine. The socket abstraction also makes it possible to support RTP over TCP in the future. Change-Id: If6cf4f42136229490186d2d2482fb4fc140c2b53 |
10 years ago |
|
|
ab3a47ae41 | finish renaming control.[ch] to control_tcp.[ch] | 13 years ago |
|
|
a050fcfa48 | rename control.[ch] to control_tcp.[ch] | 13 years ago |
|
|
5f5e158d76 | private structs make for safer threading | 14 years ago |
|
|
419f6bb230 | and the tcp controller becomes thread-safe | 14 years ago |
|
|
145bbd1f7c |
Prepare for multi-threaded operation
Introduce generic "objects" with reference counting primitives and automatic
resource deallocation when no refs are left ("garbage collection"). Overhaul
poller framework to make extensive use of these objects to allow for future
thread-concurrent operation.
No locking added anywhere yet except in poller. Poller is still not 100%
thread safe, but close.
Valgrind reports no errors or memleaks.
|
14 years ago |
|
|
dc7517121d | remove uuid helper code | 14 years ago |