Hi all,
I have some serious problems (like out-of socket errors) with the
RPCServiceClient class when I have a burst of web service calls very fast in a
row and create a new RPCServiceClient instance for each call. Normally my
application creates series of fast web service calls (to the same web service)
in a row like a "burst". Unfortunately because of the system architecture I
don't know in my module - which implements the web service request - how many
service calls will follow a certain service call. So I can not use the best
solution like creating a RPCServiceClient instance when the first call to the
web service occurs and "shut down" the RPCServiceClient instance when all
requests of this "burst" are done.
The only solution I currently have is to use a static RPCServiceClient instance
which will be created when the applciation starts and lives until the
application is shut down.This solution seems to be OK at the first glance but I
am afraid that this will result in some other problems like not freeing
ressources or other ugly side-effects.
Does anyone have some hints what I have to consider if I use a "static"
RPCServiceClient instance and which options or parameters I should use?
Any help or comment is welcome.
Thanks in advance- Marc
_________________________________________________________________
Importieren Sie ganz einfach Ihre E-Mail Adressen in den Messenger!
http://messenger.live.de/community/neuekontakte_adressimport.html
