Pooling, SOAP, etc...

[Former Member]

We have a situation where we developed an app for a customer and they were experiencing problems with connection times.

We tweaked the connection pooling code in Nco 1.x, and now they are running into problems with "maximum conversations exceeeded". We're resolving that currently, but they may want to move to 2.0.

If we do that, does anyone see significant advantage to using SOAP to do our calls. We do quite a few calls per transaction to read data, etc.

[reiner_hille-doering]

Both versions, 1.x and 2.0 support both features RFC/Soap and RFC connection pooling. In both areas version 2.0 just has some enhancements. The decision to use Soap or RFC usually depends on questions:

- Is there a Firewall between client and server that only supports Soap.

- Is the app performance critical? Usually RFC is significantly faster than Soap.