<div>
I agree with splitting the points, even though the answers were totally opposite. It appears there is no hard and fast answer - just opinions. I went with the open/close for each query. Makes for a simpler design.
</div>


I agree with splitting the points, even though the answers were totally opposite. It appears there is no hard and fast answer - just opinions. I went with the open/close for each query. Makes for a simpler design.

<div>
<div class="content wysiwyg-content">
I am developing a Web Service application using gSOAP. The application is transaction based - I know, not recommended for Web Services, just following orders. The client supports an RF network of PDAs. Typically, a handful (6?) PDAs running a query to a host DB, each PDA transmitting a request evey 3 seconds. Traffic could be considerably higher, depending on customer - out of our control.<br />
<br />
Question I have is this, should I treat each WS query as an independent query (open gSOAP, send/receive query, close gSOAP) or should I open a session and not close gSOAP until the user logs out. ie open gSOAP, run several queries, close gSOAP. Not sure what the SOA says about this. How much overhead is involved in opening and closing a SOAP transaction?<br />

</div>
</div>


I am developing a Web Service application using gSOAP. The application is transaction based - I know, not recommended for Web Services, just following orders. The client supports an RF network of PDAs. Typically, a handful (6?) PDAs running a query to a host DB, each PDA transmitting a request evey 3 seconds. Traffic could be considerably higher, depending on customer - out of our control.

Question I have is this, should I treat each WS query as an independent query (open gSOAP, send/receive query, close gSOAP) or should I open a session and not close gSOAP until the user logs out. ie open gSOAP, run several queries, close gSOAP. Not sure what the SOA says about this. How much overhead is involved in opening and closing a SOAP transaction?


Web Service design with gSOAP

C++ is an intermediate-level general-purpose programming language, not to be confused with C or C#. It was developed as a set of extensions to the C programming language to improve type-safety and add support for automatic resource management, object-orientation, generic programming, and exception handling, among other features.