Hello,
I am experimenting with Sofia-SIP and like it very much.
I am currently carrying a 'call' structure around via the nua_hmagic_t hmagic
pointer. It works well.
However, it looks like this same hmagic pointer may also be used in some
non-call situations such as registration.
In anticipation of a C++ object model, I am trying to think about what to name
a base class to be conveyed via the hmagic pointer, where derived classes will
have names suitable to their specialization.
I suspect one derived class will be 'Call', but I don't know enough yet about
Sofia SIP to anticipate proper terminology for the base class and other derived
classes alongside Call.
Any suggestions? I would like to name these things in a way that aligns well
with the Sofia-SIP conceptual model and any existing naming conventions.
Thanks.
Jim
-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Sofia-sip-devel mailing list
Sofia-sip-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
