< Previous by Date | Date Index | Next by Date > |
< Previous in Thread | Thread Index | Next in Thread > |
Thanks for the quick response! Wouldn’t it be useful to
implement a better clone functionallity, then, in order to be able to create a
real duplicate? If I would implement this, could I replace the current clone
method (in addition to add a new constructor which takes a UserProfile as
argument)? Matthias From: Scott Godin
[mailto:slgodin@xxxxxxxxxxxx] You should create one user profile for each identity (from header)
that you have. The same userprofile can be re-used for multiple
simulatenous calls. It is not really safe to be changing the default from
in a user profile while it is in use. Scott From:
resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxxx on behalf of Matthias Moetje Hi, I am just thinking about best practices for dealing with
UserProfiles. My applications must make calls with different values in the FROM
header through makeInviteSession. I specify the FROM through the UserProfile’s
setDefaultFrom method. Can I reuse the same UserProfile object without problems for
calls with different FROM header? Is it OK just to setDefaultFrom before
calling makeInviteSession or does dum use settings from the UserProfile at a
later time so that I need to create different UserProfile objects for each
makeInviteSession? The problem with the latter procedure is that the
UserProfile::clone method (or the constructor with the baseProfile parameter)
does not really clone the UserProfile (but just the settings from the Profile
class), so that the DigestCredentials collection and other properties get lost
when cloning. Thanks for any hints! Best regards, Matthias Moetje
|