Fault handling redirects in SOAPpy

[Robert Olson]

I just realized that we can similarly add proactive code to pass the 
identity down *to* the call and not deal with it on an exception. Am poking 
at that now.

--bob

At 04:07 PM 3/8/2004, Ivan R. Judson wrote:

>Oh, that's cool. I like it. I agree with Tom though; that given the use this
>should be isolated to security related exceptions (ideally those resulting
>from either an invalid proxy).
>
>--Ivan
>
> > -----Original Message-----
> > From: Robert Olson [mailto:olson at mcs.anl.gov]
> > Sent: Monday, March 08, 2004 3:59 PM
> > To: judson at mcs.anl.gov; ag-dev at mcs.anl.gov
> > Subject: RE: Fault handling redirects in SOAPpy
> >
> > At 03:51 PM 3/8/2004, Ivan R. Judson wrote:
> >
> >
> > >Looks cool; but I'm missing the motivation for it? Is
> > something broken
> > >without this?
> >
> > If we can use this, we can remove the logic for always
> > attempting the creation of a proxy certificate when the app
> > starts. This lets me make the reinitialization of certificate
> > state when it's modified by the certificate manager cleaner
> > as well (since it currently reuses the globus-startup code,
> > which will attempt to create a proxy..)
> >
> > It also leads us to more cleanly supporting choosing the
> > identity to use for a particular connection if we have
> > multiple identities in place.
> >
> > --bob
> >
> >