brainslog

Hi @xphudin, Yes, `ThreadPool` or `ExecutorService` should be good candidates. What do you think ? Would you be up to contribute on this ? That'd be awesome!

@coolface88, it's somewhat expected that Seagull and jDiameter won't work properly with TLS. IIRC in jDiameter it's being used RFC 6733 compliant TLS (CER is sent over TLS connection) while...

@aferreiraguido, good job so far! Thanks for the hard work. I have made some inline comments in the changes, please review them and let me know your thoughts and/or fix...

Hi @aferreiraguido! Sorry for the late review, but here are some of my notes. I thought about doing them inline, but I think it's easier to follow on a single...

Hi @jehanzebqayyum, thanks for your interest in this contribution. As per your queries, I will try to explain as I can. > 1- Client and Server both are using same...

@jehanzebqayyum, regarding TLS we are working in parallel on issue #14 . The idea will be to have both ways working. We surely want RFC 6733 behavior to be the...

@jehanzebqayyum, both server and client need to prepare for TLS after sending/receiving the CEA, and setup the HandshakeCompletedListener. As for the check of EXPERIMENTAL_RESULT, it's likely just a "fallback" mechanism...

@jehanzebqayyum, I don't think we have any ready, will need to prepare it. Or maybe @coolface88 who's working on #14 might have some already ? If not, I'll try to...

The idea would be to reduce the actual configuration values lookup, this was an old issue so the whole context behind it and how I thought it could work isn't...

Hi @chathsuom. Yes, jDiameter uses it's own configuration loading mechanism, independent from jboss. For this to work we will need to specify a configuration change listener (see https://github.com/RestComm/jdiameter/blob/6e911bf9fe3b7d3e7c9e88ef1b50f88265027c82/core/jdiameter/impl/src/main/java/org/jdiameter/server/impl/helpers/EmptyConfiguration.java#L244) for the...