>Excuse me I have not read the list for some weeks...
>Which "string properties"?
Just adding 'properties' member variable of type PStringToString
to CallRec class. Then developers could store additional call
information they need inside this dictionary - without need
of modifying RasTbl.cxx each time.
Let's take an example - I would like to do call accounting.
I need RADIUS 'Acct-Session-Id' generated for each call.
Moreover - I need this value to be generated on call setup
and preserved to the call end (rather obvious;). If I had
string properties I could write somethin like:
callptr call = CallTable::Instance()->FindCallBy...(...);
call->SetProperty("Acct-Sesstion-Id",mysessionid);
and then in some other place:
storedSessionId = call->GetProperty("Acct-Session-Id");
Without properies I would need to add new member fields
to CallRec everytime I need to store additional information.
After some time (release cycle) I could decide that some
"string properties" are very useful and should be moved
to member fields in order to improve performace/reduce
memory overhead.
---
Michal Zygmuntowicz
-------------------------------------------------------
This SF.net email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software. http://www.objectstore.net/sourceforge
_______________________________________________
List: Openh323gk-users@lists.sourceforge.net
Archive: http://sourceforge.net/mailarchive/forum.php?forum_id=8549
Homepage: http://www.gnugk.org/
