Click here to view and discuss this page in DocCommentXchange. In the future, you will be sent there automatically.

SQL Anywhere 11.0.1 (Français) » QAnywhere » Mobile web services » Writing mobile web service applications

 

Multiple instances of the service binding class

You should create an instance of the service binding class for each QAManager. If a mobile web services application has more than one instance of a service binding class, it is important that the service ID be set using the SetServiceID method. For example:

service1.SetServiceID("1")
service2.SetServiceID("2")

The service ID is combined with the service name to form a queue name for receiving web service responses. It is important that each instance of a given service has a unique service ID so that a given instance does not get responses to requests made by another instance of the service. If the service ID is not set, it defaults to "". The service ID is also important for preventing multiple applications that use the same service from conflicting with each other, since queue names persist messages in the message store across applications that are transient.