RE: [reSIProcate] DUM: handling createAppDialogSet() failure

["Derek MacDonald" <derek@xxxxxxxx>]

There needs to be an AppDialogSet present for DUM to function successfully;
we could have a catch that creates the default AppDialogSet when such an
exception occurs.  Otoh, I can't really think of a circumstance where
failing the creation of an AppDialogSet(barring allocation problems) is the
correct thing to do. Do you have a use case for this?

--Derek

> -----Original Message-----
> From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:resiprocate-
> devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Dmitry Semyonov
> Sent: Thursday, November 04, 2004 5:41 AM
> To: resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> Subject: [reSIProcate] DUM: handling createAppDialogSet() failure
> 
> Hello.
> 
> It is assumed that createAppDialogSet() always returns "good" pointer.
> Should an exception be thrown from overridden createAppDialogSet()
> function in case when dialog set creation fails by some reason?
> 
> The same question applies to createAppDialog().
> TIA.
> 
> --
> ...Bye..Dmitry.
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel