On Friday 06 June 2008, Daniel-Constantin Mierla wrote: > [..] > I have to second Henning here in regard to a proper discussion may lead > to better solution. Maybe I am missing something, but from what I have > seen in the description and the code, binding this route to TM solve > just few of the demands. It is called after the buffer of the message to > be sent is built. > > IMO such route shall be available for all messages sent by openser, so > we get access in it to what is going to be sent on the network. There > are solutions to detect that the message is locally generated (e.g., > only one via header), to decide there what to do. Apart of the benefits > brought now, siptrace will work for all messages, we can get make > available the destination ip and port, therefore filtering is more > flexible, also logging/accounting get access to this information. > > I believe that this is a real topic for discussion, and if it is really > important, we can postpone one or two days the freeze for the right > decision. Leaving a half solution for a full release is not a right > approach.
Hello Daniel, i agree here to you, of course. But i think that further delaying of the freeze is also not a good solution. So i think we'll probably need to live with this solution for 1.4. Cheers, Henning _______________________________________________ Devel mailing list Devel@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/devel
