On 6/13/2010 8:47 AM, Antonio Anderson Souza wrote: > Nowadays it returns directly what the RTPProxy Error codes, but it's > really a good idea create an Object and group the errors by type! great > idea! > > I asked for the list of possible error codes to document it better, and > in the next step we can create a better error handling and reporting > with objects, types, messages, etc.
I agree. The problem here is that if we document it as it is now then it becomes semi-official API. And suddenly all those numbers that as I explained were used just for debugging purposes become magic constants that we will have support from one release to another. Regards, -- Maksym Sobolyev Sippy Software, Inc. Internet Telephony (VoIP) Experts T/F: +1-646-651-1110 Web: http://www.sippysoft.com MSN: [email protected] Skype: SippySoft _______________________________________________ Devel mailing list [email protected] http://lists.rtpproxy.org/mailman/listinfo/devel
