GroupWise Web Services is based on HTTP as the transport layer. HTTP 1.1 provides persistent connections to the POA. The <connection>keep-alive</connection> line establishes this persistent connection. If the connection is not used, it times out after 30 minutes of inactivity. Most development frameworks reestablish the connection for an application after the timeout. You should test your application to ensure that it behaves correctly after a timeout.
There is also a SOAP session connection. This session is a GroupWise connection to the POA. The session times out after 30 minutes. If your application needs to keep this GroupWise session alive, the getTimestampRequest method provides a noop parameter. The noop option keeps the session and HTTP connections open.
The following is an example of HTTP headers in a login request and response:
<HTTPHeaders> <content-type>text/xml; charset=utf-8</content-type> <content-length>809</content-length> <soapaction>"loginRequest"</soapaction> <user-agent>Java/1.5.0_04</user-agent> <host>188.8.131.52:8080</host> <accept>text/html, image/gif, image/jpeg, *; q=.2, */*; q=.2</accept> <connection>keep-alive</connection> </HTTPHeaders> <HTTPHeaders> <date>Tue, 10 Oct 2012 12:01:19 GMT</date> <server>Windows GroupWise POA 7.0.1</server> <content-type>text/xml; charset=utf-8</content-type> <content-length>940</content-length> <pragma>no-cache</pragma> </HTTPHeaders>