axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject Re: Call initilize and uninitialize
Date Tue, 25 May 2004 11:10:50 GMT
Each remote method invocation need to do following,

1. Create a new MessageData object.
2. Use initialized Serializer/Deserializer objects.
3. Create a new ClientEngine object which holds all above.

I think we should avoid connecting to the server whenever possible. For an
example if the transport provides the facilities like "HTTP KEEP ALIVE"

> Hi All,
>    In the generated client stubs, I see that the Call object is
> initialized and uninitilized for
> every call.
>    I think this is too much for every call (there can be performace issues
> as well). Also initing
> and uniniting per metod call causes stub wide info to be erased between
> calls. We should only
> create and close the connection per each method call.
>    Why not we initialize the Call once the stub class is created and
> ininitialize it in the stub
> destructor and call connect and disconnect for evry call?
> Thanks,
> Samisa...
> __________________________________
> Do you Yahoo!?
> Friends.  Fun.  Try the all-new Yahoo! Messenger.

View raw message