Hi All,
I am looking into the Call::initialize() method that is being called
within the client side generated code,
prior to each method invocation.
Basically if we have 2 method calls that we could invoke, and in the
client program we execute both those methods,
we will be cal
It looks to me like with each call to Call::Initialize() if a ClientAxisEngine object exists it is deleted and then a new one created and initialized (I am not sure whether ClientAxisEngine->Initialize() caters for this).
Shouldn't it be that if a AxisClient object exists it should be reused by int
To: Apache AXIS C Developers List
Subject: RE: Restructuring
Call::initialize
Yes, ClientAxisEengine is
deleted for each method, despite the fact we are using the same Stub object.
Deleting the engine every
time has to be removed and move some of the init logic which is one off to the
> have not yet planned how to measure it.
>
>
>
> Thanks,
>
> Samisa…
>
>
>
> -Original Message-
> From: Samisa Abeysinghe [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 30, 2005 4:34 PM
> To: Apache AXIS C Developers List
> Subject: RE: Restru
> them on each method call.
> >
> > My feeling is that this will lead to improved performance, though I
> > have not yet planned how to measure it.
> >
> >
> >
> > Thanks,
> >
> > Samisa…
> >
> >
> >
> > --
call.> > > > My feeling is that this will lead to improved performance, though I> > have not yet planned how to measure it. > > > > > > > > Thanks,> > > > Samisa…> > > > > > > > -Original Message-> > From: Samisa Abeysinghe [mailt
on each method call.
> >
> > My feeling is that this will lead to improved performance, though I
> > have not yet planned how to measure it.
> >
> >
> >
> > Thanks,
> >
> > Samisa…
> >
> >
> >
> > -Original Message-
> &g
