| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
previous one
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
conventions
|
|
|
|
| |
properly per message instead of per session
|
|
|
|
| |
only have an address
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
the expense of having two session objects for what is pretty much the same address; however, as the inbound one is not really validated and might not work due to NAT, this actually does make sense
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
adding additional check for messages being enqueued for destroyed sessions
|
| |
|
|
|
|
| |
think I fixed a leak
|
|
|
|
| |
theory at least)
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
indentation, doxygen -- may help/fix #3591
|
|
|
|
| |
testcases yet
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
much as possible
|
|
|
|
| |
happen...
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
ATS_Information struct
|
|
|
|
| |
even fully address #3247
|