emiago
Server Response Middlewares
Server response Middlewares seem to be not implemented yet, do we have any plans? This is very useful for implementing SIP capture (pushed to Homer).
middlewares are just extra function calling. Wrapping as such should not be big deal. I find them very hard to track when it comes to debuging in some frameworks.
Still it would be benefit to keep library minimalistic and not force some pattern.
If your goal is just to trace every message, then you need to look deeper. Server is not where you should hook stuff for SIP traffic. ;)
On other hand creating this homer support would be interesting to be part of sipgox package. If you have some library that could be reused, I may contribute to this?
If your goal is just to trace every message, then you need to look deeper. Server is not where you should hook stuff for SIP traffic. ;)
Yes, it would be more appropriate if there were some hooks at the transport layer. I initially tried the Server layer hooks just because I happened to notice them, but you're right – it's not the best way.
On other hand creating this homer support would be interesting to be part of sipgox package. If you have some library that could be reused, I may contribute to this?
I'm interested in integrating Homer into sipgox. I have implemented Homer's HEP3 protocol. Can you share your design thoughts and how we need to implement it?
First of all we need library or implement HEP wrapping. So if you can have this shared, that would 90% job. I can rethink what would be best way to plug in this.
Where I need to understand better is storage requirements. It would be better to abstract but as this is Homer thing anyway maybe we can leave it out.