Does Software AG plans to create more robust (may be non HTTP) java client API for Tamino?
The present API is too slow, possibly due to numerous HTTP connections which are opened for any reason. It seems that API creates a new HTTP connection per element when we retrieve them via TaminoResult.nextElement() method.
Looking forward for your reply.
Thank you.
quote:
Originally posted by Terry Dye:
[QUOTE] Originally posted by Day:
Does Software AG plans to create more robust (may be non HTTP) java client API for Tamino?
The present API is too slow, possibly due to numerous HTTP connections which are opened for any reason. It seems that API creates a new HTTP connection per element when we retrieve them via TaminoResult.nextElement() method.Looking forward for your reply.
Thank you.
First, I would support a native API, rather than a wrapped http client (or the source to the current client to fix the delete problem). But perhaps Software AG found the http server as the simplest solution to manage their APIs. It is the lowest common denominator for fire wall problems. Perhaps a comment from the developers?
Second, why not use the TaminoResult.getDocument() and manipulate the data with JAXP? JAXP is meant for such objects and would cut down your http connections to Tamino. Look at the JAXP 1.1 examples for an example. There are also code examples within this community. [/QUOTE]